# CRM reimplementation introduction email | SourceX

Canonical: https://refer.sourcex.si/resources/crm-reimplementation-introduction-email
Last updated: 2026-11-05

Write to the owner who decides about the old Salesforce org, not to the admin, and keep it to three short paragraphs: what the admin confirmed about opportunity stage history and closed outcomes, what the reimplementation plan currently does with it, and an offer to introduce SourceX with your referral interest disclosed and a description-only ask. Are stage transitions and final outcomes preserved beyond current account fields? The usual answer, "yes, the old org has them; the new org's load plan may not", is the email's first paragraph.

This draft is part of the [introduction email worksheet](/resources/a-reusable-worksheet-for-introduction-email-preparation). It comes after the [CRM reimplementation meeting agenda](/resources/crm-reimplementation-meeting-agenda) ends with a yes; the [moment guide for Salesforce architects](/guides/moment-crm-reimplementation-salesforce-architects) covers how the subject comes up in a project.

## The draft

Illustrative. Replace each brace from the admin's answers and your notes. Aim for under 200 words.

> Subject: {company}'s deal history in the old org, before cutover on {cutover_date}
>
> Hi {owner_first_name},
>
> Following our conversation: {admin_name} confirmed the current org has kept the stage history of every opportunity since {first_year}, including closed-won and closed-lost outcomes and loss reasons from {loss_reason_year}. The migration plan loads open opportunities and current fields only, so that history stays behind unless you decide otherwise before the old org is retired.
>
> If keeping it is worth a conversation, SourceX licenses approved business data directly from companies for AI training and evaluation, and runs the agreement, rights review, data preparation, delivery and payout. Nothing leaves {company} without a signed agreement. To be clear about my position: I am a SourceX referral partner, and SourceX may pay me a reward if a qualifying license completes. It pays that separately, it never reduces what {company} would receive, and it does not change our project scope.
>
> SourceX would start with a description only: years covered, rough deal counts, which org holds them and who can approve a discussion. Reply "yes" and I will introduce you, or "not now" and I will drop it.
>
> {your_name}

## Line-by-line annotation

| Line | Why it is there | What never goes in it |
| --- | --- | --- |
| Subject line | Names the company, the record and the dated event, so it is findable later | "Monetize", "opportunity" or a figure |
| "{admin_name} confirmed..." | Attributes each fact to the person who checked it in the org | Opportunity names, amounts or customer accounts |
| "Stage history of every opportunity since {first_year}" | States the answer to the qualifying question in owner language | A claim you have not confirmed, such as "complete" or "clean" |
| "Loss reasons from {loss_reason_year}" | Signals the outcome has a reason, not only a status | Loss reason text or examples |
| "The migration plan loads open opportunities and current fields only" | Explains why the decision is time-bound, using the project's own plan | Criticism of the migration vendor or the plan's authors |
| "Unless you decide otherwise before the old org is retired" | Puts the choice with the owner, tied to a real event | Invented deadlines or "last chance" wording |
| The SourceX sentence | One accurate line on what SourceX does | Buyer names, AI labs or demand claims |
| The disclosure sentences | Makes your connection and the payer explicit before any introduction | "I may be compensated" without naming SourceX |
| "Does not change our project scope" | Separates the referral from your paid architecture work | Discounts, bundled fees or scope trade-offs |
| "A description only" | Puts the metadata boundary in writing | Requests for exports, reports or sandbox access |

## Three facts the email rests on

The draft is only as good as the facts in paragraph one, so confirm each with the admin before writing it.

1. **Stage history exists and has not been purged.** Salesforce Help says a Stage History entry is added whenever a user changes an opportunity's Amount, Probability, Stage or Close Date, and that opportunity stage history is not deleted automatically, unlike field history on other objects. In the API it is the OpportunityHistory object, which sits apart from the opportunity record, so a load plan that maps opportunity fields will not carry it unless someone adds it.
2. **Other tracked fields may not go back as far.** Without Field Audit Trail, field history is kept for up to 18 months in the interface and up to 24 months through the API. If the owner hears "full history" about every field, the email has overstated it. The [field history retention explainer](/questions/salesforce-field-history-tracking-retention) covers this limit.
3. **The load plan really excludes it.** Ask the migration lead, not the statement of work. If closed opportunities and their history are already being archived, rewrite paragraph one to say where.

None of these needs you to open a deal. The [metadata-only Salesforce inventory template](/resources/a-metadata-only-salesforce-inventory-template-for-company-introductions) records the answers.

## What never goes in the email

- **Anything exported from the org.** No reports, CSVs, dashboards or screenshots, even when the admin offers one.
- **Customer or rep names.** Describe the record type and the years, never the people.
- **A reward figure as a promise.** The default is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap and paid only after the conditions in the terms are met. Illustrative only: a $400,000 Actual Supplier Payout would mean a $70,000 reward. Quoting numbers in the first email invites the owner to treat them as likely.
- **SourceX on copy.** Wait for the owner's yes.

Why the disclosure is written out: the FTC's Endorsement Guides call for clear and conspicuous disclosure of a connection the audience would not expect, and they count the chance of payment as one. Whether that reaches a private email is for your own advisers; writing it plainly removes the question.

## Adjusting the draft to what the architect found

| What you found | Change to the draft |
| --- | --- |
| The old org was rebuilt once before | Add "with an earlier org archived in {year}" and leave it out of the ask until someone confirms it can be read |
| Loss reasons are free text before a certain year | Replace "loss reasons from {year}" with "a loss reason picklist since {year}, free text before" |
| Stage history is already in the archive plan | Change paragraph one to name the archive location and drop "stays behind" |
| The owner wants the CRO to lead | Address both and name the CRO as SourceX's contact |
| A large customer contract restricts reuse | Say so in one line; SourceX's rights review will test it |

The sibling [engineering system modernization email](/resources/engineering-system-modernization-introduction-email) shows the same structure for a PLM project. The [CRM archive context checklist](/resources/crm-reimplementation-archive-context-checklist) tracks the dates; [Salesforce data archiving](/guides/salesforce-data-archiving) covers storage choices.

## When the owner says yes

Sign the Channel Partner Agreement, then submit the authorized contact through your partner account and step back. 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. Fit: 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. More plays are on the [Salesforce consulting partner page](/for/salesforce-consulting-partner-referral-program).

## 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.

Once the admin has confirmed the stage history and the owner has agreed to hear more, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [terms](/terms) before you send the draft.

## 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://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.5
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
