Destructive Changes & DevOps
NEWA pioneer feature allowing for the systematic deletion of data.
Overview
A pioneer feature allowing for the systematic deletion of data. This is critical for DevOps processes (cleaning an org before a fresh load) or removing deprecated catalog data.
Warning: Use With Caution
Destructive operations permanently delete data. Always test in a sandbox environment first and ensure you have backups before running destructive operations in production.
How It Works
Select Plan Type
Works on top of Standard Plans, Deep Clone Plans, or Custom Plans.
Set Mode
Set the migration mode to "Destructive".
Execution
The tool identifies records based on the plan and deletes them in the correct reverse-dependency order (children first, then parents).
Configuration
Destructive Plans
Build specific plans for data cleanup operations. Define exactly which objects and records should be deleted.
Batch Size
Configurable in Admin Settings. Default: 200 records per batch.
Use Cases
DevOps Workflows
Clean an org before a fresh data load to ensure a pristine environment.
Catalog Cleanup
Remove deprecated products, pricing rules, or catalog configurations.
Test Data Removal
Clean up test data from sandbox environments after testing cycles.