Integrity controls during bulk legacy loads
Key Takeaway
Move integrity checks out of the bulk load itself, and store each legacy ID in an External ID field on the parent so child records find the correct parent.
Large legacy migrations face a trade-off. Validation rules, workflow rules, triggers, and sharing calculations protect data quality, but they can slow a bulk load to a crawl. The safe approach moves those checks out of the load itself. You clean and sequence data before the load, suspend rules during the load, then rebuild relationships and turn the rules back on afterward.
How to plan a lean load
Loading lean is the best practice for a large data volume (LDV) migration. You load only the data and configuration that business-critical operations need. You also load it as fast as possible, which shrinks how much data must be kept in sync.
- Identify the business-critical operations before users move.
- Identify the minimal data set and configuration those operations need.
- Build a data and configuration strategy on those requirements.