Back to all articlesCRM migration

Decide What to Migrate Before Mapping CRM Fields

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

If every source record is considered necessary, field mapping becomes a debate about preserving the old system rather than supporting work in the new one. Before mapping fields, classify the source data into four dispositions: import, archive only, exclude from the migration package, or hold for an exception decision. Give each category an explicit rule, destination, owner, and verification method.

The deciding question is not whether a record exists. It is whether someone needs it to perform a named task in the new CRM, or whether it supplies an essential relationship or context for a record that does. Historical reference can often have a separate destination. Unreadable or unresolved material needs a visible exception path, not a silent import failure.

The worksheet below shows how to make those choices defensible before field mapping starts. It addresses migration scope, not ongoing retention policy or legal obligations. Excluding something from an import does not authorise deleting its source.

1. Start with the work the new CRM must support

Write a short list of tasks that must work at cutover. These tasks become the test for inclusion. Avoid requirements such as “keep all history,” which do not identify what a user needs to accomplish.

A hypothetical sales team might name these tasks:

  • Review every genuinely active opportunity and its next action.
  • Identify the correct account, contact, and owner for each included opportunity.
  • Read the recent activity needed to continue a live conversation.
  • Find selected closed outcomes for an agreed reporting comparison.
  • Retrieve older supporting material from a separate archive when necessary.

Ask the owner of each task what would fail if a proposed data category were absent. “We have always had it” is not a workflow dependency. “The account manager needs the last agreed proposal to continue this negotiation” is one.

This distinction also prevents excessive trimming. An old account record may still be essential because an active opportunity depends on it. Scope cannot be decided by age alone.

2. Define dispositions before discussing destination fields

Use a small, consistent vocabulary so that “not imported” does not become an ambiguous outcome.

  • Import: Load into the working CRM because it supports an agreed task or an essential relationship.
  • Archive only: Keep outside the operational CRM in an agreed reference destination, with a way to locate and interpret it.
  • Exclude from the migration package: Do not include in the load or migration archive. Record the reason and the source location; this decision does not instruct anyone to delete it.
  • Hold for exception review: Do not load until a named person resolves a specific uncertainty. The hold needs an owner and decision deadline.

An archive is not simply an export file someone hopes to find later. Specify its location, permitted audience, index, and retrieval method. Preserve source identifiers and enough context to explain what a record refers to. Test whether the intended user can locate and open it.

A hold is not a fifth destination called “later.” Its possible outcomes must be one of the other dispositions, or an explicitly approved deferral with a documented operational consequence.

3. Filled hypothetical scope worksheet

Fictional worked example: The following company, rules, quantities, and dates are hypothetical. A sales team is preparing a CRM cutover on 1 October 2026. It wants an operational pipeline, selected recent closed outcomes, and a searchable reference archive. These choices illustrate a design; they are not recommended universal time limits.

Each worksheet entry contains a selection rule, disposition, destination, decision owner, and verification method. A team can copy these entries into its own scope register and replace the assumptions.

Active opportunities

  • Selection rule: Import opportunities marked open only when the sales owner confirms an active next action. Include their required account and contact relationships. Send unconfirmed open records to exception review rather than assuming the status is accurate.
  • Disposition and destination: Confirmed records go to the new CRM's opportunity dataset, with linked account and contact records. Unconfirmed records remain in the exception register pending a decision.
  • Hypothetical quantity: Of 420 open records, 360 are confirmed active and 60 require review.
  • Decision owner: Sales operations lead, with the responsible sales manager confirming disputed activity.
  • Verification: Reconcile the approved source-ID list against loaded opportunity IDs. Check that every imported opportunity has the required parent relationship, a valid owner assignment, and its agreed next-action information.

Closed records

  • Selection rule: Import closed opportunities dated from 1 October 2024 through the cutover snapshot for the agreed recent-outcome comparison. Archive earlier closed opportunities. Include older records only through an approved dependency or workflow exception.
  • Disposition and destination: Recent closed records go to the new CRM; older records go to a restricted reference archive with a source-ID index and linked account identifiers.
  • Hypothetical quantity: Import 1,100 recent closed records and archive 4,800 older ones.
  • Decision owner: Sales operations lead and the owner of the reporting comparison.
  • Verification: Reconcile counts by closed outcome and date range. Compare agreed amount totals using the same currency and amount definitions. Retrieve a sample of archived records by source ID and account.

Orphaned activities

  • Selection rule: Hold activities whose account, contact, or opportunity reference cannot be resolved. Repair a link only when there is reliable evidence of the intended parent. Do not attach activities using a similar name alone.
  • Disposition and destination: Activities with verified links follow the scope of their parent record. Unresolved activities go to a restricted archive with their original reference values and a note that the relationship is unresolved.
  • Hypothetical quantity: Of 240 orphaned activities, 90 have verified links and 150 remain unresolved.
  • Decision owner: Data steward; the relevant business owner approves disputed relinking.
  • Verification: Record the evidence for each repaired relationship. Check that every imported activity resolves to its intended destination parent and that archived unresolved activities retain their original identifiers.

Obsolete custom fields

  • Selection rule: Exclude fields with no approved workflow, reporting use, or relationship dependency from the destination schema. Preserve populated values in the archive when historical interpretation requires them. Route a newly identified use case to exception review.
  • Disposition and destination: Do not create obsolete fields in the new CRM. Store relevant historical values with their source records and a field dictionary in the archive. Empty, unused fields are excluded from the migration package.
  • Hypothetical quantity: Of 18 obsolete fields, six contain historical values to archive and 12 are empty and unused.
  • Decision owner: Business process owner, with the reporting owner checking downstream use.
  • Verification: Review known reports and exports for dependencies. Confirm the excluded fields are absent from the load specification, and retrieve archived values using their original field names and descriptions.

Unreadable attachments

  • Selection rule: Do not load files that cannot be opened or whose contents cannot be verified. Attempt recovery from the source or request a replacement from the owner. Do not treat the filename as evidence of the file's contents.
  • Disposition and destination: Recovered, readable files follow their parent record's scope. Unrecoverable files remain outside the CRM in a restricted unresolved-file area, with a manifest listing source ID, parent reference, filename, and recovery result.
  • Hypothetical quantity: Of 35 unreadable attachments, 20 are recovered and 15 remain unresolved.
  • Decision owner: Migration lead, with the business owner deciding whether missing content blocks the associated workflow.
  • Verification: Open recovered files and confirm their parent links. Reconcile every original attachment to a recovered file or an unresolved manifest entry. Explicitly report the 15 unresolved items rather than counting them as successful transfers.

4. Resolve dependencies without importing everything

The worksheet makes primary decisions, but related data can expand the scope. An included opportunity may need an account, a contact, activities, and attachments. Those records can point to still more records. Without a stopping rule, dependency handling recreates an all-record migration.

Define the minimum relationship set needed for each approved task. Include the account required by an active opportunity, but do not automatically include every historical activity on that account. Evaluate the activities against their own rule.

Keep original source identifiers in a reconciliation register so the team can trace a source record to its destination, archive entry, exclusion, or hold. If duplicate source records will become one destination record, document that consolidation explicitly. A count mismatch can be expected, but it must be explainable.

Do not manufacture parent records merely to satisfy an import requirement. A placeholder account might make a load pass while placing unrelated activity under a misleading customer identity. Either establish the relationship, use an approved unresolved-data destination, or keep the item out of the operational load.

5. Make exceptions small, owned, and reviewable

An exception request should state the source IDs or reproducible selection rule, the task at risk, the requested disposition, the related records required, and the verification check. It also needs a requester, decision owner, deadline, and recorded outcome.

For example, in this hypothetical scenario, an account manager requests one older closed opportunity because its proposal is needed for a live renewal. The approval could include that opportunity and the specific proposal, without importing every older opportunity on the account.

The requester should not silently expand the scope by changing an export filter. Have the business owner approve the need and the migration lead assess the additional load, relationship, and testing work. A rejected request should retain its reason so it is not repeatedly reopened without new evidence.

Set a decision cutoff before the final extraction. Late requests need an explicit choice: accept and retest, defer to a later load, or reject. If an unresolved item is essential to a cutover task, escalate the task's readiness rather than hiding the missing data.

6. Verify scope separately from import success

A technically successful import proves neither that the correct records were selected nor that excluded records have a usable destination. Test selection, disposition, and usability separately.

  1. Reproduce the selection. Save the scope version, source snapshot reference, filters, and approved ID lists. A second reviewer should be able to explain why a record qualifies.
  2. Reconcile dispositions. Every inventoried source item should have one primary disposition. Separate unresolved holds from completed outcomes.
  3. Reconcile destinations. Match approved import IDs to load results and archive IDs to the archive index. Document deliberate consolidation rather than treating it as unexplained loss.
  4. Test boundaries. Check records just inside and outside date rules, stale open opportunities, missing parents, and approved exceptions. These cases expose ambiguous selection logic.
  5. Test the task. Have the responsible business user continue a hypothetical active opportunity and retrieve an archived closed record. Record missing context and retrieval failures.

Useful measures include disposition coverage, unresolved exception count, missing required relationships, and archive retrieval failures. Set acceptance criteria before the rehearsal so a disappointing result cannot be relabelled as acceptable after the fact.

7. Freeze the scope, then map fields

Once the scope is approved, field mapping becomes a narrower job: translate the records and values that have an agreed destination. Keep the approved scope version beside the mapping specification, and require a scope-change decision when mapping reveals a new dependency.

If a rehearsal exposes a mistake, recover at the rule level. When too many stale opportunities qualify, revise the active-opportunity rule and regenerate the selection. When too few records qualify, identify the missing workflow or dependency. Avoid patching individual rows without recording why; those fixes are easily lost in the final extraction.

Recalculate the affected populations, update the worksheet, and rerun the relevant relationship and retrieval checks. Do not broaden the entire migration merely because one category needs correction.

Next action: Before the next mapping session, assign an owner to each of the five worksheet categories and produce its candidate count, proposed disposition, destination, and verification check. Report how many categories are approved and how many records remain on hold. Begin mapping only the approved populations; keep unresolved decisions visible rather than converting uncertainty into permanent CRM structure.

CRM migrationData scopeData qualityMigration planning

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications