Data migration
Importing data, cleaning it, and validating the results.
Overview
Migration succeeds when you import in stages and validate each batch. Clean data early to avoid noise in workflows and reporting.
Plan the order: core objects first, relationships second, and activities last.
What you’ll do
- Export legacy data to CSVs with normalized headers and formats.
- Map fields to Forge objects and run a dry import in a test workspace.
- Validate results with sampling and fix duplicates before go-live.
Best practices
- Import accounts and contacts first, then deals and activities.
- Standardize phone, email, and date formats to avoid errors.
- Keep a rollback plan for the first week after launch.