CRM reimplementation referral meeting agenda: 30 minutes on stage history for Salesforce architects

Short answer

Run a half-hour sponsor conversation in five timed blocks, one question each. The first five minutes pin down the load plan; minutes 5-12 put the core question, "Are stage transitions and final outcomes preserved beyond current account fields?"; 12-18 probe tracking and backups; 18-24 settle timing and ownership; the last six minutes cover your disclosure and end in a decision: introduce, revisit by a dated deadline, or stop. Nobody opens a record.

Visual briefFull-size diagram
A meeting clock drawn as a ring of five segments that fill in turn: load plan (0-5 minutes), stage history (5-12), field history and exports (12-18), old org and owner (18-24) and disclosure and decision (24-30).
The 30-minute agenda as a ring. Block lengths are a guide; protect the last six minutes.

This script is one of the working tools for the CRM reimplementation guide for Salesforce architects. Afterwards, the archive context checklist tracks each answer against the project calendar.

Before the meeting: the room and the one-line invite

Four people are enough. More turns the slot into a design review.

SeatWhy they are in the roomBlocks they carry
CRO, CFO or ownerDecides what happens to the old org and whether to discuss licensing4, 5
Salesforce admin of the old orgKnows how long the org has run, past purges and export jobs2, 3
Migration lead or data architect (often you)Knows what the load plan carries into the new org1, 2
Sales operations leadKnows how loss reasons and stage changes are actually recorded2, 4

Leave out the implementation vendor's delivery team and any outsourced sales development agency. Their roles can be noted later; in the room they turn a history question into a scope negotiation.

Invite text that works: "Thirty minutes on what happens to closed-deal history in the old org. Descriptions only, nothing exported." It tells the owner the meeting costs them nothing.

The five blocks at a glance

Illustrative. An architect is running the agenda for a fictional 310-person building products wholesaler whose old Salesforce org dates from 2013.

MinutesBlockThe questionWho answers
0-5Load planWhich objects and which years will the new org load, and with current values or history?Migration lead
5-12Stage historyAre stage transitions and final outcomes preserved beyond current account fields?Admin and migration lead
12-18Field history and exportsWhich other changes are tracked, and are export files kept anywhere?Admin
18-24Old org and ownerHow long will the old org stay readable, and who owns sales history?Owner and sales operations
24-30Disclosure and decisionWould the company like to hear how licensing approved business data works?Owner

Ask the sales operations lead to keep time and stop each block on the minute. Notes go in four columns: block, answer, who said it, open item with an owner.

What a strong answer sounds like in each block

Minutes 0-5: load plan

Strong: "Open opportunities with full detail, closed ones from the last three years as reference records with final values, nothing older." You are listening for the words "final values", because that phrase means the path is not coming. A vague answer here is the first open item.

Minutes 5-12: stage history

Strong: "The old org has stage history back to 2013, and it is not in the load template. We had not discussed archiving it." Salesforce Help documents that 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. So in a long-running org, this is often the deepest record of how deals moved. A weak answer is "the outcomes are all there", which answers half the question.

Minutes 12-18: field history and exports

Strong: "We track discount and competitor fields, but without Field Audit Trail. We run a weekly export and nobody saves the files." Two documented limits shape this block. 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. A weekly export is not an archive unless each file is saved somewhere.

Minutes 18-24: old org and owner

Strong: "Read-only for twelve months after cutover, then decommissioned when the license ends. The CFO decides; two enterprise customer contracts restrict reuse." You need the decommissioning trigger and the person behind it more than a precise date.

Minutes 24-30: disclosure and decision

Say three things before asking for a decision. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout. You are a SourceX referral partner and may receive a reward if a qualifying license completes; SourceX funds it separately and it never reduces the company's payout. The reimplementation does not depend on the answer.

Signals that should close the meeting early

What you hearWhat it tells youWhat to write down
"The old org was decommissioned before the project started."The history no longer exists in SalesforceClosed; note any external archive mentioned
"We rebuilt the org in 2022 and history was not carried then either."The path covers only recent yearsRecord the span; continue only if the owner wants to
"Sales is run by a distributor network that owns the accounts."Rights may sit with third partiesNote the arrangement; stop
"We have about 35 employees."Below the 50 full-time baselineClosed
"Not something we want to discuss."The owner has declinedClosed; the project carries on unchanged

The decision the meeting should produce

Close with one of three outcomes, each with a name and, where relevant, a date tied to the company's own plan.

OutcomeWhen it fitsWhat follows
Introduce nowStage history exists for several years, the owner is identified and opts inSubmit the introduction through your partner account
Revisit by a dateThe archive decision or the decommissioning date is still openFollow up before the documented read-only end
StopThe owner declines, or size or rights rule it outRecord the reason and close

For "introduce now", fit comes first: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license 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. Unknown until SourceX reviews it: whether the stage history fits current dataset needs, the rights review on customer terms, de-identification and any offer.

Sign the Channel Partner Agreement before submitting. 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 $250,000 Actual Supplier Payout to the company would mean a $62,500 default reward, paid after the conditions on the rewards page are met.

The same agenda shape appears in other settings, such as the sell-side kickoff agenda and the portfolio review agenda. If loss reasons turn out to live in free-text notes, the lead qualification notes data type explains what makes such notes useful, and the Salesforce consulting partner page covers the wider channel.

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 meeting closed on "introduce now", register as a partner, confirm the company against who qualifies and read the program terms before the old org's read-only period ends.

  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

Can this run as part of a data migration design workshop?

It can, as the last half hour, with the owner joining only for it. Running it inside the mapping session tends to pull the conversation back to field mappings and validation rules.

What if the sponsor wants to see a sample opportunity history first?

Decline politely. The meeting works on descriptions: which objects, how many years, which org and who owns them. Any look at records happens later, between SourceX and the company, if the company chooses.

Is it a problem if the answer to block two is 'we have not decided'?

No. 'Not decided, the migration lead will confirm by the design sign-off' is a usable answer. Write the name and the date beside it.

Sources

  1. help.salesforce.com/s/articleView
  2. help.salesforce.com/s/articleView
  3. help.salesforce.com/s/articleView
  4. refer.sourcex.si/terms

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