# CRM reimplementation: keep stage history | SourceX

Canonical: https://refer.sourcex.si/guides/moment-crm-reimplementation-salesforce-architects
Last updated: 2026-11-04

Often not. A Salesforce reimplementation usually loads accounts, contacts and opportunities as they stand today: current stage, amount, owner and close date. The stage transitions that led to each win or loss, and the context around them, live in history records the new design may never carry across. Architects can ask the owner whether that path will survive, map the answer from metadata, and introduce the decision-maker to SourceX if the company wants to explore licensing.

## Are stage transitions and final outcomes preserved beyond current account fields?

Ask the question in exactly those words during design, before the data migration plan is signed off. The honest answer is often "the outcome, yes; the path, we had not thought about it."

The distinction matters because the two live in different places. In Salesforce, Help documents that a new Stage History entry is added whenever a user changes an opportunity's Amount, Probability, Stage or Close Date, that admins cannot choose which of those fields are tracked, and that stage history is not automatically deleted. The developer documentation describes the OpportunityHistory object as the stage history of an opportunity, a separate object from the opportunity itself. That makes the old org's stage history one of the more durable records it holds. Other tracked fields behave differently: without Field Audit Trail, Salesforce retains field history for up to 18 months in the interface and up to 24 months through the API.

So in an old org, the path to each outcome may stretch back many years in stage history, while changes to other fields fade after two. In a new org, the question is whether any of it arrives at all. A migration that inserts opportunities with their final values creates fresh records; the new org's own stage history starts on load day and says nothing about the years before. Ask the architect who owns the migration design whether the old stage history is carried across, archived, or left behind when the old org is switched off.

### Annotated record chain: one closed opportunity

Illustrative. A fictional 240-person industrial equipment distributor is reimplementing Salesforce after years of customization. One opportunity from 2021:

| Date | Stage | Amount | Close date | Where it is recorded |
|---|---|---|---|---|
| Mar 2021 | Prospecting | 180,000 | Sep 2021 | Stage history |
| May 2021 | Proposal | 210,000 | Sep 2021 | Stage history |
| Aug 2021 | Negotiation | 195,000 | Dec 2021 | Stage history (close date pushed) |
| Nov 2021 | Negotiation | 195,000 | Mar 2022 | Stage history (pushed again) |
| Feb 2022 | Closed Lost | 195,000 | Feb 2022 | Stage history, plus a loss reason field |

The current record says only the last row: Closed Lost, 195,000. The four rows above it show how the deal actually moved: the amount rose and fell, the close date slipped twice, and it was lost in the end. A reimplementation that loads only current fields keeps the outcome and drops the path. Activities, emails and notes tied to the same opportunity add context, and they have their own migration decisions.

## Why is stage-change history easy to overlook in a reimplementation?

Because nothing in the new org needs it on day one. Reimplementation scope is driven by what sales needs to work tomorrow: open pipeline, active accounts, current owners, the new stage model and its validation rules. Closed opportunities are often loaded as reference records with their final values, and the history object is not part of the standard load template.

Three design choices make the gap wider. First, a new stage model: when the company renames or merges stages, old transitions no longer map cleanly, so the team skips them rather than translate them. Second, a fresh org rather than an in-place cleanup: the old org becomes read-only for a while and is then decommissioned, and its history goes with it. Third, export habits: 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. A weekly export is therefore not an archive unless someone saves each file.

None of this is a failure by the project team. Stage history is simply owned by nobody on the plan, which is why one question from the architect is often the first time the owner hears about it.

## Four metadata questions to ask the sponsor

Keep the conversation at metadata level: what exists, how much, how long, which system and who owns it. Four questions cover it:

1. **Path or outcome?** Will the old org's stage history and loss reasons be migrated, archived outside Salesforce, or left in the old org when it is retired?
2. **How far back?** Roughly how many years of closed opportunities exist, in how many orgs, and has any history been purged or rebuilt before?
3. **How long reachable?** When does the old org go read-only, when is it decommissioned, and who decides?
4. **Whose records?** Who owns sales history, and do any customer contracts or privacy commitments limit how it can be used?

Write down the answers as the sponsor gives them, ranges included. Do not ask for a report, a sample or a screenshot; those belong to SourceX's own review with the company, if the company chooses one. The [CRM discovery questions](/resources/crm-discovery-questions) add prompts for wider CRM projects, and the [field history retention explainer](/questions/salesforce-field-history-tracking-retention) covers the 18 and 24 month limits in more depth.

## How do you disclose the reward and get the owner's permission?

Ask permission before you mention SourceX at all, and disclose your interest in the same breath. A workable form: "There is a separate question about whether that history has value outside the company. May I tell you about one option? I should say I am a referral partner, so I may receive a reward if it leads anywhere."

If the sponsor says yes, explain in two sentences that SourceX licenses approved business data directly from companies for AI training and evaluation and pays the company for it, and that any reward to you is funded separately by SourceX and never deducted from the company's payout. If the sponsor says no, the item closes and the reimplementation carries on unchanged; the archive question was still worth asking for the project's sake.

Keep the reward description exact. The default is the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, with no cap across all agreements and renewals. Illustrative only: a $250,000 payout to the company would mean a $62,500 reward. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.](/rewards) explains.

## Does the company qualify, and who can authorize a licensing discussion?

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.

| Question | What an architect can usually confirm | What stays unknown until SourceX reviews |
|---|---|---|
| Which records exist? | Opportunities with stage history, loss reasons, related activities | Whether buyers need that record type |
| Who owns them? | The company, subject to customer contract terms | The rights review result |
| Who can authorize? | CEO, often the owner | Dataset scope and de-identification |
| How much and how long? | Rough opportunity count and years covered | The company's offer and any reward |

The [company introduction checklist for CRM records with deal outcomes](/resources/a-company-introduction-checklist-for-crm-records-with-deal-outcomes) turns this into a pre-introduction list. Related moments are covered in [CRM consolidation after an acquisition](/guides/crm-consolidation-after-acquisition), [Salesforce data archiving](/guides/salesforce-data-archiving) and, for ERP projects, [how NetSuite consultants spot referral opportunities](/guides/how-erp-consultants-spot-referral-opportunities-during-netsuite-projects). The [Salesforce consulting partner page](/for/salesforce-consulting-partner-referral-program) and the [partner hub](/for) cover the wider channel.

Sign the Channel Partner Agreement before submitting the introduction. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner credited per company.

## Go deeper on CRM reimplementation records

- [CRM reimplementation meeting agenda](/resources/crm-reimplementation-meeting-agenda): a timed agenda for the owner meeting where stage history and the referral option come up.
- [CRM reimplementation archive context checklist](/resources/crm-reimplementation-archive-context-checklist): a checklist of the scope, dates and export details to confirm before the old org is retired.

## 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 sponsor confirms years of stage transitions and outcomes exist and wants to explore licensing before the old org is switched off, [register as a partner](/register), confirm fit on [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce them.

## Sources

- https://refer.sourcex.si/terms
- 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
