Back to all articlesCRM migration

Close a CRM Migration With Evidence Rather Than an Informal Sign-Off

Alactic Editorial9 min read

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

The destination CRM is live, but someone still opens the old system to find a proposal, a manager has an unexplained record-count difference, and approvals are scattered across messages. Calling the migration complete leaves the business with an unresolved dependency rather than a clear handover.

Use an acceptance packet: a versioned collection of reconciliation results, historical-access tests, defect dispositions, exception approvals, and source-exit conditions. Every material discrepancy needs a status, an accountable owner, and evidence supporting that status.

The standard is practical: another reviewer should understand what was accepted, what remains unavailable, and which decisions are still blocked without reconstructing a message thread. This is an operating practice, not a claim about controls available in any particular CRM.

1. Define three separate acceptance decisions

Start with a scope statement naming the source, destination, migrated populations, cutover boundary, exclusions, and evidence version. Acceptance might cover accounts, contacts, opportunities, activities, attachments, and older notes. It should not quietly expand into a review of every business result since launch.

A disappointing sales forecast is not automatically a migration defect. An opportunity amount changed incorrectly during transformation may be.

  • Destination acceptance: Is the migrated scope usable and sufficiently verified, subject to explicitly approved exceptions?
  • Migration closure: Are all closure criteria met, with no unresolved migration work except obligations formally transferred through an approved handoff?
  • Source dependency exit: Can required work and historical retrieval proceed without the old CRM?

These decisions need not occur together. However, temporary source access must not disappear into an ambiguous sign-off. If migration closure is allowed before source exit, require an approved handoff naming the remaining obligation, receiving owner, access arrangements, evidence needed for exit, review checkpoint, and escalation route.

The worked example below uses a stricter rule: unresolved migration-related source dependencies block migration closure as well as source exit. No transfer of those obligations has been approved. Destination acceptance can still be considered separately.

None of these decisions authorizes record disposal. Retention and deletion decisions are outside this packet.

2. Give each register status an evidence threshold

Keep statuses few and distinguish completion from intention:

  • Resolved defect: A correction has been applied, independently retested, and accepted by the named reviewer against the agreed criterion.
  • Accepted exception: A known departure remains, but an authorized decision-maker has accepted its specific impact and any workaround.
  • Open blocker: An unmet criterion prevents one or more named decisions. It has an owner and a required next test.
  • Pending verification: Evidence or review is incomplete. A correction awaiting review belongs here, not under resolved defects.

Status, severity, and decision impact are separate fields. An inaccessible historical attachment might not prevent routine destination use, but it can still block closure and source exit. A formatting difference might be acceptable if information remains readable and the responsible business owner approves the limitation.

Assign both a remediation owner and an acceptance authority. The person correcting a mapping should not automatically have authority to accept lost information. Record evidence versions and completed review outcomes; a future review date is not evidence that a criterion has passed.

3. Reconcile stable populations and meaningful relationships

Identify the source snapshot, destination load, and cutover boundary before comparing results. Explain how changes made during cutover were captured. Otherwise, reviewers may be comparing populations that changed at different times.

Matching headline counts are insufficient. Counts can agree while records are duplicated, relationships are incorrect, or important values are missing. Check several layers:

  • Population: Account for in-scope records, exclusions, merges, rejects, and loaded records.
  • Identity: Map source identifiers to destination identifiers, including approved many-to-one merges.
  • Relationships: Check that contacts, activities, and attachments connect to their intended parent records.
  • Meaning: Verify agreed interpretations of stages, ownership, dates, amounts, and statuses after transformation.

Explain differences rather than selecting a convenient tolerance after seeing the results. Permission to accept optional formatting differences does not authorize missing ownership or inaccessible proposals.

Use full-population comparisons where feasible and targeted user tests where interpretation matters. State the limits of each method: successful retrieval of selected historical items does not prove that every historical item is present.

4. Test historical access as a user task

An export file is not proof of usable history. Test whether an intended user can locate a record, identify the relevant item, open it, and understand its context.

Use tasks such as retrieving the last proposal on a closed opportunity or reading a former owner's note. Capture the expected item, tested role, retrieval route, observed result, and evidence reference. Record failures as precisely as successes: finding an attachment label but failing to open its contents is a failed retrieval.

Test representative permissions rather than relying only on an administrator. Include a negative case where a role should not see restricted material. OWASP's authorization guidance recommends least privilege, deny-by-default access, and permission checks on every request. These are design recommendations, not evidence that a particular product implements them.

If history will remain outside the destination, document who retrieves it, how requests are handled, and what happens when retrieval fails. A temporary source login can be a workaround, but it remains a source dependency until a replacement route is accepted.

5. Work through a filled acceptance register

Fictional worked example: All names, quantities, dates, identifiers, and outcomes in this example are hypothetical. They illustrate a recommended process, not Alactic capabilities or customer results.

Packet AP-03 covers accounts, contacts, opportunities, activity notes, and attached proposals. Its boundary is source snapshot S-01 plus change inventory DELTA-01. The following filled entries can be reused as a register structure: criterion, status, finding, owner, authority, evidence, review outcome, and blocked decisions.

AR-01 — Account population discrepancy

  • Criterion: Every in-scope source account identifier is accounted for.
  • Status: Resolved defect.
  • Finding: The source contained 4,820 accounts; the initial destination load contained 4,808. Twelve rejects resulted from an owner mapping error.
  • Owner and authority: Maya, migration lead; Ellis, sales operations acceptance authority.
  • Evidence and completed review: FIX-01 v2 records the correction. Independent reviewer Ren completed comparison RET-01 v2, accounting for all 4,820 source identifiers without unexplained variance. Ellis reviewed and accepted RET-01 v2 on 16 September; decision recorded in APR-01 v1.
  • Decision impact: No remaining block to destination acceptance, migration closure, or source exit from this entry.

AR-02 — Historical note formatting

  • Criterion: Historical notes retain their content, context, and usable readability.
  • Status: Accepted exception.
  • Finding: Forty-six notes lost bullet formatting. REC-02 v1 found their text and parent links intact. Selected long-note retrieval tests in HIST-02 v1 passed, although scanning was harder.
  • Owner and authority: Theo, migration analyst; Ellis, acceptance authority.
  • Approval: EXC-02 v1 records Ellis's completed acceptance of the readability impact for the listed notes, with no formatting repair required.
  • Decision impact: Blocks none of the three decisions. Approval does not cover missing text, unreadable content, or unlisted notes.

AR-03 — Proposals available only in source

  • Criterion: Required proposals can be retrieved through an accepted replacement route.
  • Status: Open blocker.
  • Finding: Twenty-eight attachments appear in the source inventory but cannot be opened through the intended destination route. HIST-03 v1 records a failed sales-user retrieval.
  • Owner and authority: Priya, technical migration owner; Jordan, commercial operations acceptance authority.
  • Current evidence: REC-03 v1 lists affected identifiers. DEP-01 v1 documents restricted source lookup as a temporary workaround, accepted by Jordan only for continued destination use.
  • Decision impact: Blocks migration closure and source dependency exit. Does not independently block destination acceptance under the documented workaround. No post-closure handoff has been approved.
  • Required next evidence: Account for every listed attachment and demonstrate retrieval through the agreed replacement route using the intended role. Record any item-specific exception separately. Priya's next checkpoint is 18 September.

AR-04 — Restricted history permissions

  • Criterion: Intended roles can retrieve restricted history, while disallowed roles cannot.
  • Status: Pending verification.
  • Finding: History is present, but only administrator access has been tested.
  • Owner and authority: Ren, access-control owner; Jordan, acceptance authority.
  • Evidence required: Execute TEST-04 against role matrix ACL-01 v1, record allowed and denied retrieval results, investigate mismatches, and obtain Jordan's review.
  • Decision impact: Blocks destination acceptance, migration closure, and source exit. No permission-test pass has yet been recorded.

AR-05 — Changes during cutover

  • Criterion: All changes within the agreed cutover boundary are accounted for.
  • Status: Resolved defect.
  • Finding: Seventeen opportunity edits occurred after the initial snapshot. The first delta load missed three stage changes.
  • Owner and authority: Maya, migration lead; Ellis, acceptance authority.
  • Evidence and completed review: DELTA-01 v2 defines the bounded inventory. Ren independently reran field comparison RET-05 v2 after correction and accounted for all seventeen edits. Ellis reviewed and accepted that result on 16 September in APR-05 v1.
  • Decision impact: No remaining block from this entry. Later destination edits are outside this comparison boundary.

AP-03 decision summary: Two resolved defects, one accepted exception, one open blocker, and one pending verification. Destination acceptance remains pending AR-04; AR-03's workaround is documented, not repaired. Migration closure is blocked by AR-03 and AR-04. Source dependency exit is also blocked by both. None of the three decisions is approved in this packet version.

6. Keep exception approvals narrow

An exception approval should identify the affected population, unmet criterion, observable impact, workaround, and person accepting that impact. Add a review trigger when a workaround relies on temporary access or a future repair.

A broad statement accepting historical issues cannot establish whether inaccessible proposals were knowingly accepted or overlooked. Reference exact register entries and evidence versions. In the example, AR-02 accepts formatting loss for listed notes; it cannot be used to clear AR-03.

Repairing every presentation imperfection may not justify extending migration work. Missing information needed for a retrieval task requires a different decision. Base that distinction on affected work and evidence, not project age. If an exception is declined, return the entry to an unresolved status and identify its decision impacts.

7. Gate source exit with a controlled rehearsal

Before proposing source exit, confirm that required records and history are retrievable through accepted routes, intended users have tested access, and unresolved entries no longer depend on the source.

Reconcile the final cutover boundary as well. Continued source editing can create competing populations. Where appropriate, stop routine source editing through an authorized operational change rather than assuming users have stopped.

Run a bounded rehearsal in which representative users perform agreed tasks without routine source access, while a controlled fallback remains available. If retrieval fails, record the task, use the authorized fallback, and reopen the relevant blocker. A quiet period alone is not evidence that dependency has ended.

Under AP-03's strict closure rule, AR-03 must pass its replacement-route tests or receive an explicit new disposition before closure can proceed. A target date does not satisfy that gate.

8. Publish decisions against the packet version

The decision record should name the packet version, scope, approved exceptions, unresolved entries, authorities, and effective date. State destination acceptance, migration closure, and source exit separately, even when all three have the same outcome.

Include a reopening rule. If a newly discovered missing item contradicts accepted scope or evidence, reopen its register entry and reassess affected decisions. If the problem arose from a later operational change, route it outside migration closure.

Before the acceptance meeting, move unresolved issues from messages into the register. Assign each an owner, blocked decisions, required evidence, and reviewer. Review blockers and pending verifications first. The meeting should produce decisions supported by reviewed evidence—not another request for everyone to confirm that things look fine.

CRM migrationData reconciliationMigration acceptanceOperational handover

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