A Pipeline is configured as a sequentially ordered list of #Batch Executables that migrates data from one org to another while preserving all parent–child relationships. The execution order ensures parent records are processed before their dependent child records, with each Executable’s field mappings easily configured to maintain the relationships.
Overview
General Use Case
Use a Pipeline to orchestrate multi-step, cross-org data migrations—running sequential #Batch Executables that preserve parent–child relationships by leveraging External IDs, VLOOKUPs, and Record Type developer names in field mappings. For large volume data (e.g., more than 1 million records), enable Bulk API and tune batch size to achieve faster, more efficient execution.
Video Demo
Prerequisites
Target Org Custom Fields
Account.SourceSystemID__cText(18)Contact.SourceSystemID__cText(18)Downloadable Executables
DataMigration.Current.OrgBWalkthrough
1
Pipeline - DataMigration.Current.OrgB
2
New Executable - Contact.Migration.Current.OrgB
3
Batch Settings
4
Retrieve
5
Mapping
