# CRM reimplementation meeting agenda | SourceX

Canonical: https://refer.sourcex.si/resources/crm-reimplementation-meeting-agenda
Last updated: 2026-11-04

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.

This script is one of the working tools for the [CRM reimplementation guide for Salesforce architects](/guides/moment-crm-reimplementation-salesforce-architects). Afterwards, the [archive context checklist](/resources/crm-reimplementation-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.

| Seat | Why they are in the room | Blocks they carry |
|---|---|---|
| CRO, CFO or owner | Decides what happens to the old org and whether to discuss licensing | 4, 5 |
| Salesforce admin of the old org | Knows how long the org has run, past purges and export jobs | 2, 3 |
| Migration lead or data architect (often you) | Knows what the load plan carries into the new org | 1, 2 |
| Sales operations lead | Knows how loss reasons and stage changes are actually recorded | 2, 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.

| Minutes | Block | The question | Who answers |
|---|---|---|---|
| 0-5 | Load plan | Which objects and which years will the new org load, and with current values or history? | Migration lead |
| 5-12 | Stage history | Are stage transitions and final outcomes preserved beyond current account fields? | Admin and migration lead |
| 12-18 | Field history and exports | Which other changes are tracked, and are export files kept anywhere? | Admin |
| 18-24 | Old org and owner | How long will the old org stay readable, and who owns sales history? | Owner and sales operations |
| 24-30 | Disclosure and decision | Would 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 hear | What it tells you | What to write down |
|---|---|---|
| "The old org was decommissioned before the project started." | The history no longer exists in Salesforce | Closed; note any external archive mentioned |
| "We rebuilt the org in 2022 and history was not carried then either." | The path covers only recent years | Record 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 parties | Note the arrangement; stop |
| "We have about 35 employees." | Below the 50 full-time baseline | Closed |
| "Not something we want to discuss." | The owner has declined | Closed; 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.

| Outcome | When it fits | What follows |
|---|---|---|
| Introduce now | Stage history exists for several years, the owner is identified and opts in | Submit the introduction through your partner account |
| Revisit by a date | The archive decision or the decommissioning date is still open | Follow up before the documented read-only end |
| Stop | The owner declines, or size or rights rule it out | Record 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](/rewards) are met.

The same agenda shape appears in other settings, such as the [sell-side kickoff agenda](/resources/sell-side-kickoff-meeting-agenda) and the [portfolio review agenda](/resources/portfolio-review-meeting-agenda-private-equity). If loss reasons turn out to live in free-text notes, the [lead qualification notes data type](/data-types/lead-qualification-notes-data) explains what makes such notes useful, and the [Salesforce consulting partner page](/for/salesforce-consulting-partner-referral-program) 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](/register), confirm the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before the old org's read-only period ends.

## Sources

- https://help.salesforce.com/s/articleView?id=sf.opp_history.htm&language=en_US&type=5
- 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
