What this service solves
Move one clean CRM object into a new system through a rehearsed import. The field map tells the team where values will go, the rehearsal identifies missing or unsupported values, and the final reconciliation distinguishes records that loaded from records that were rejected.
What you get
Mapped and migrated object
Approved records are loaded using the reviewed mapping after the rehearsal and sign-off.
Reconciliation and rejects
The owner receives source and destination counts, disposition of skipped or rejected records, and a reject export for follow-up.
What’s included
Profile an export and map fields
Profile the export for required fields, types, duplicates, and values the destination may not support. Match source identifiers to the destination's import model.
Perform a test import
Rehearse the import in the agreed test area. Review what loaded, what was skipped, and what needs a mapping or source-data correction.
Load approved data and reconcile counts and rejects
Run the approved import in the cutover window. Reconcile the accepted and rejected counts and preserve the rejected rows for the owner's decision.
How implementation works
Profile and map
Review a sample export, destination definitions, and field ownership. Agree on how to handle repeat or pre-existing records.
Rehearse and obtain sign-off
Run one rehearsal and obtain sign-off on its results, the accepted source set, and the cutover plan.
Import and reconcile
Import the approved data and reconcile counts and representative field values before handing off.
Technical considerations
- Import identity and destination limits
- Check which identifiers the destination uses to create or match an existing record and agree on how to handle conflicts before rehearsal. Review supported import field types, authorized write access, and relevant limits.
- Cutover review
- Agree with the owner on the approved source snapshot and how to handle changes made after it is taken. Verify the destination's test results before approving the live import window.
Systems, inputs & prerequisites
Export and destination access, field mapping owner, sample data, and a cutover window.
- Authorized source export and destination access, a sample file, and an owner who can approve the mapping.
- A cutover window, the intended handling of existing destination records, and acceptance rules for invalid rows.
Starting scope & pricing
Base scope
One clean source CRM, one standard object, up to 5,000 records, one rehearsal and one cutover.
Illustrative workflow
Export
Prepare the agreed source object and verify the reference identifiers.
Rehearse
Check how approved fields and picklist values appear after a test import.
Reconcile
Import the approved records, compare counts, and export the rows that need correction.
Validation & handover
- Compare mapped values for representative rehearsal records with the source export, including required fields, picklist values, and an expected rejection.
- Review rehearsal counts and unresolved rows with the mapping owner before sign-off on the final import and cutover window.
- Reconcile the approved source set with loaded, skipped, and rejected records after import. Hand over the field map, report, and reject export.
Limitations & possible extras
Limitations
Multi-object relationships, activity history, enrichment, and additional cutovers require separate scoping. Source quality and destination write limits must be checked before cutover.
Source quality, API limits, and write access must be checked before cutover.
Possible extras
Multi-object relationships, activity history, enrichment, or additional cutovers.
Questions about this service
What happens to rejected rows?
Keep them in a separate export with the observed reason where available. The owner can decide whether to correct the data and arrange a later import.
Can we bring over related deals and activity history?
The starting scope covers one clean source CRM and one standard object. Related objects and activity history need a relationship and sequencing plan with separate scope.
What if the destination already has some of the same contacts?
Use representative records to confirm the match key, then agree which rows to skip or update before rehearsal. Hold ambiguous matches for the owner.
What if a mapping issue appears during rehearsal?
Review the rejected rows or unexpected values with the mapping owner before sign-off. Confirm the approved source set and mapping before cutover.