CRM reimplementation: how Salesforce architects check whether stage history survives

Short answer

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.

Visual briefFull-size diagram
One illustrative opportunity shown twice: in the old org as five dated stage transitions ending in Closed Lost with a loss reason, and in a new org as a single current record where the path that led to the outcome is missing unless the migration carries it.
Illustrative opportunity. Stage history behavior from Salesforce Help, checked 2026-10-18.

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:

DateStageAmountClose dateWhere it is recorded
Mar 2021Prospecting180,000Sep 2021Stage history
May 2021Proposal210,000Sep 2021Stage history
Aug 2021Negotiation195,000Dec 2021Stage history (close date pushed)
Nov 2021Negotiation195,000Mar 2022Stage history (pushed again)
Feb 2022Closed Lost195,000Feb 2022Stage 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 add prompts for wider CRM projects, and the field history retention explainer 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.

QuestionWhat an architect can usually confirmWhat stays unknown until SourceX reviews
Which records exist?Opportunities with stage history, loss reasons, related activitiesWhether buyers need that record type
Who owns them?The company, subject to customer contract termsThe rights review result
Who can authorize?CEO, often the ownerDataset scope and de-identification
How much and how long?Rough opportunity count and years coveredThe company's offer and any reward

The 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, Salesforce data archiving and, for ERP projects, how NetSuite consultants spot referral opportunities. The Salesforce consulting partner page and the partner hub 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

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, confirm fit on who qualifies, and read the program terms before you introduce them.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. 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.

Common questions

Is stage history the same as field history tracking?

No. Salesforce keeps opportunity stage history in its own record, which logs changes to Amount, Probability, Stage and Close Date and is not automatically deleted. Field history tracking covers other fields an admin chose to track and, without Field Audit Trail, is retained for up to 24 months through the API.

Can an architect pull a sample of closed opportunities to show SourceX?

No. Partners stay at metadata level: record types, counts, years covered, the system and the owner. The company's authorized contact decides whether to talk to SourceX, and SourceX handles any review of records with the company.

Does a reimplementation have a deadline that forces a decision?

Only the company's own: the cutover date, when the old org becomes read-only or is decommissioned, and when its license ends. If that date has passed and the old org is gone, the honest finding is that the history no longer exists.

Sources

  1. refer.sourcex.si/terms
  2. help.salesforce.com/s/articleView
  3. developer.salesforce.com/docs/atlas.en-us.object_reference.meta/objec…
  4. help.salesforce.com/s/articleView
  5. help.salesforce.com/s/articleView

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment