# CRM reimplementation archive checklist | SourceX

Canonical: https://refer.sourcex.si/resources/crm-reimplementation-archive-context-checklist
Last updated: 2026-11-05

Only if someone confirms it before the legacy org is retired: stage history lives in a separate history object that a load plan built on current values can leave behind. Tick off twelve items across three checkpoints: before the program is announced, before go-live, and before the legacy org is retired. Each item has a named person who confirms it and a stated consequence if it slips, so the countdown doubles as a small risk log for the project. The company supplies every date; you supply the questions, and nothing is exported or opened to answer them.

This checklist sits under the [CRM reimplementation guide for Salesforce architects](/guides/moment-crm-reimplementation-salesforce-architects). The first answers usually come out of the [timed sponsor conversation](/resources/crm-reimplementation-meeting-agenda); this page carries them forward to retirement day.

## Set the clock: three dates and who owns them

Pin down three calendar points, and who set each, before ticking anything. A blank is an answer too.

| Milestone | Where the date usually lives | If nobody has set it |
|---|---|---|
| Announcement | The program charter or the sponsor's kickoff note | You are early; work through milestone one without hurry |
| Cutover | The data migration plan and go-live runbook | Record who owns the go-live decision |
| Switch-off | The old org's license end or a decommissioning ticket | Leave it blank; the item is "find out who decides" |

Give each item a status: **confirmed** by someone with authority, **unknown** with a named person who will find out, or **at risk** because the current plan loses it. A mapping spreadsheet is not confirmation; a person is.

Keep the record in a short sheet that describes configuration and ownership only. No opportunity names, amounts, customer names or screenshots go into it.

## Milestone one: before the reimplementation is announced

Nothing about the old org's history has been decided yet, so questions here sound like good housekeeping rather than a challenge to the plan.

| Confirm | Owner | If skipped |
|---|---|---|
| How many years the old org has run, and whether it was ever rebuilt or merged | Salesforce admin | The team assumes a longer history than really exists, or misses an older org |
| That stage history exists for closed opportunities and has never been purged | Salesforce admin | The deepest record of how deals moved is never counted |
| Where loss reasons live: a picklist, free text or nowhere | Sales operations lead | Outcomes survive without the reason for them |
| Who owns sales history and whether customer contracts limit reuse | Owner or counsel | Rights questions arrive after an introduction, not before |

The stage history row has firm documentation behind it. Salesforce Help says a Stage History entry is added whenever a user changes an opportunity's Amount, Probability, Stage or Close Date, that admins cannot choose those fields, and that stage history is not automatically deleted. The developer reference describes it as the OpportunityHistory object, separate from the opportunity record itself.

## Milestone two: before cutover to the new org

Once the load plan is fixed, closed history tends to become "reference data" and the separate history object drops out.

| Confirm | Owner | If skipped |
|---|---|---|
| Whether OpportunityHistory is in the load plan, archived elsewhere or left behind | Migration lead | The new org starts its own history on load day and the old path is never carried |
| A written map from old stage names to the new stage model | Sales operations lead | Old transitions cannot be read once stages are renamed or merged |
| Which other fields are tracked and whether Field Audit Trail is in use | Salesforce admin | Changes older than the retention window are assumed to exist |
| Whether export files are saved after each run, and under whose user the job is scheduled | Salesforce admin | The team relies on files that were already overwritten |

Two documented limits drive rows three and four. Without Field Audit Trail, field history is retained for up to 18 months in the interface and up to 24 months through the API. And Salesforce's Data Export FAQ notes that export files are removed as soon as a new export is queued, and that a scheduled export fails if the user who scheduled it is deactivated. The [field history retention explainer](/questions/salesforce-field-history-tracking-retention) goes into the first limit in more depth.

## Milestone three: before the old org is switched off

This is the last point at which anything can change. Items still open here may be lost for good.

| Confirm | Owner | If skipped |
|---|---|---|
| How long the old org stays read-only and what triggers its retirement | Owner or CFO | History disappears with a license renewal nobody connected to it |
| Where any archive of stage history, loss reasons and activities will live | Migration lead or IT | The archive exists but nobody can find or read it |
| That the admin account running exports stays active until the last one is saved | IT | A departing admin's deactivation stops the final export |
| Who can authorize a licensing discussion about the archived history | CEO (in an owner-run company, the owner) | An interested company has nobody able to say yes |

Items still at risk here belong in the company's own retirement plan. The [CRM consolidation guide](/guides/crm-consolidation-after-acquisition) covers the related case where two orgs are merged rather than one rebuilt.

## Reading the finished checklist and deciding what comes next

Illustrative. A fictional 270-person specialty chemicals distributor finished the checklist across its three milestones. The summary its architect read back to the CFO:

| Area | State | Note |
|---|---|---|
| Org history, 2014 onward | Confirmed | One rebuild in 2018; earlier org archived as a backup file |
| Stage history on closed opportunities | Confirmed | Not purged; excluded from the load plan |
| Loss reasons | Partial | Picklist since 2019, free text before |
| Stage name mapping | Unknown | Sales operations to draft before cutover |
| Field history beyond two years | At risk | No Field Audit Trail |
| Ownership | Partial | Two key accounts restrict reuse by contract |

That is a sound metadata-level description. If the CFO wants to explore licensing and the CEO agrees, three steps follow.

**Disclose.** Tell the owner you are a SourceX referral partner. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout. If a qualifying license completes and every payment condition is met, SourceX may pay you a reward that it funds separately and never deducts from the company's payout.

**Check fit.** The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Demand, the rights review and any offer stay unknown until SourceX reviews the application.

**Introduce.** Sign the Channel Partner Agreement first, then submit the authorized contact. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. Illustrative only: a USD 800,000 Actual Supplier Payout on a company's first qualifying transaction would mean a USD 120,000 default reward (15%, which exceeds USD 50,000 plus 5%); there is no cap, and the USD 50,000 floor applies once per company, not on repeats. The [rewards page](/rewards) lists every condition. For the handoff itself, the [CRM migration handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-a-crm-migration) and the [introduction checklist for CRM records with deal outcomes](/resources/a-company-introduction-checklist-for-crm-records-with-deal-outcomes) fit alongside this page, and the [CRM discovery questions](/resources/crm-discovery-questions) help earlier in the project.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the checklist shows stage history will outlast the switch-off and the owner wants to talk, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [program terms](/terms) before you make the introduction.

## Sources

- https://help.salesforce.com/s/articleView?id=sf.opp_history.htm&language=en_US&type=5
- https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_opportunityhistory.htm
- https://help.salesforce.com/s/articleView?id=xcloud.tracking_field_history.htm&language=en_US&type=5
- https://help.salesforce.com/s/articleView?id=000383962&language=en_US&type=1
- https://refer.sourcex.si/terms
