# Policy migration introduction email, annotated | SourceX

Canonical: https://refer.sourcex.si/resources/policy-system-migration-introduction-email
Last updated: 2026-11-04

Write to the underwriting or operations leader who can authorize a discussion, after your conversation established whether policy versions link to the decisions behind them. Use a subject naming the cutover, one paragraph on what the policy admin team said about endorsement history, one on SourceX with your reward interest disclosed, and one offering an introduction that asks only for a description. Attach nothing and name no policy. The draft and a line-by-line commentary follow.

The draft is part of the [policy system migration guide for insurance software consultants](/guides/moment-policy-system-migration-insurance-software-consultants), which sets out the version-to-decision map. It usually follows the [policy system migration meeting agenda](/resources/policy-system-migration-meeting-agenda).

## The draft, ready for your placeholders

Replace each brace with what the company told you. Underwriting leaders forward email to counsel, so write as if a lawyer will read it.

> Subject: Underwriting decision history before {legacy_system} cutover on {cutover_date}
>
> Hi {first_name},
>
> Thank you for including {admin_lead} and {uw_lead} on Tuesday. Before conversion locks, we asked one thing: are policy versions in {legacy_system} still linked to the decisions behind them? They described referral notes and rating worksheets tied to mid-term endorsements for {lines} since {first_year}, while older renewals hold documents only.
>
> SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Nothing is shared unless {company} agrees terms, and policyholder data is handled in that review. For transparency: I am a SourceX referral partner and may receive a reward from SourceX if a qualifying license completes. SourceX pays it separately, it never reduces what {company} would receive, and it has no connection to the conversion work.
>
> I can introduce you if helpful. SourceX would start from a description: lines and years with linked history, a rough count of policy transactions, where the decision notes sit and who can approve a conversation. No policy files. Reply "yes" or "not now".
>
> {your_name}

## Line-by-line commentary

| Line | What it does | What must stay out |
|---|---|---|
| Subject with system and cutover date | Anchors the email to a documented conversion event | Words like "monetize" or a dollar amount |
| "Thank you for including..." | Credits the facts to the company's own people | Names of brokers, insureds or underwriters outside the meeting |
| "Before conversion locks" | Explains why now without inventing pressure | A date that the project has not confirmed |
| The version-to-decision question | Uses the meeting's exact wording | A judgment that the history is valuable |
| Referral notes and worksheets tied to endorsements | Names the record types at metadata level | Policy numbers, claim numbers, premium figures |
| "Older renewals hold documents only" | Shows the gap honestly | Advice to change the conversion design for the referral's sake |
| The SourceX sentence | Says exactly what SourceX does | Named AI labs or claims that interest is certain |
| "Policyholder data is handled in that review" | Answers the first worry an insurance leader has | Promises about de-identification outcomes |
| Disclosure sentences | States your interest before any introduction | "I may benefit" without naming who pays |
| "No connection to the conversion work" | Keeps your consulting role separate | Discounts or fee offers tied to a referral |
| The description-only ask | Sets the metadata boundary | A request for a sample endorsement or a data extract |
| "Yes or not now" | Offers an easy decline | Chasers, deadlines, "last chance" |

### Why the email says "linked" and not "policy data"

Every insurer has policy data; the distinction worth an introduction is the link. The NAIC glossary defines an endorsement as an amendment or rider that adjusts coverage and takes precedence over the general contract, so each endorsement is a decision point. Systems record them as transactions: in Guidewire PolicyCenter's Cloud API, a policy change starts with an effective date and creates a job of type PolicyChange. Whether the referral note or rating override behind that job is linked depends on configuration and habit. The email repeats what the admin lead described about that link and nothing more. The [underwriting notes data type page](/data-types/underwriting-notes-ai-training) covers why the reasoning beside a policy matters.

### Why the disclosure sits in the middle paragraph

The FTC's Endorsement Guides call for clear and conspicuous disclosure of an unexpected connection between an endorser and a seller that could affect how a recommendation is weighed, and they include the chance of payment. Putting the sentence next to the description of SourceX, rather than in a footer, makes it impossible to miss. Ask your own advisers whether the guides apply to your situation.

## Swaps when the facts differ

| Situation | Edit |
|---|---|
| The company is an MGA writing on carrier paper | Add after the disclosure: "Your carrier agreements may decide what can be reused; SourceX's rights review starts there." |
| Decision notes live in email, not the policy system | Replace "tied to mid-term endorsements" with "kept in account mailboxes keyed to the policy number" |
| The legacy system will stay read-only for years | Drop "before conversion locks" and write "while {legacy_system} remains readable" |
| Only one line of business has links | Name that line only and drop the plural |
| The leader prefers a colleague to lead | Address both and name the colleague as SourceX's contact |
| The company is an agency, not a carrier | Replace underwriting worksheets with "service and endorsement requests" and see the [agency service request page](/data-types/insurance-agency-service-requests-ai) |

The [introduction email builder](/tools/introduction-email-builder) fills braces from your notes, and the [wealth advisor introduction email](/resources/wealth-advisor-business-owner-client-introduction-email) shows the same disclosure pattern in another profession. Brokers with commercial clients can compare the [commercial insurance broker partner page](/for/referral-program-for-commercial-insurance-brokers).

## What you must know before sending

- **Which records exist:** lines, years and the form of the decision context (referral queue, worksheet, note), described by the company.
- **Who owns them:** the company, its carriers, or both. For MGAs, carrier agreements matter.
- **Who can authorize:** the named recipient of this email.
- **Whether the company fits:** 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: demand for endorsement decision histories, the rights review result, the de-identification scope, any offer and any reward. If the [archive context checklist](/resources/policy-system-migration-archive-context-checklist) shows the links are being dropped at cutover, the email should say so.

## After a reply

A "yes" means you submit the introduction through your partner account with the recipient's details, then let SourceX lead. A "not now" means you note the date and leave it. Sign the Channel Partner Agreement before submitting. Credit goes to the first valid introduction within the 90-day window, recorded when the company submits a verified application, with one partner per company. Illustrative only: if the company were paid $250,000 for a qualifying completed handoff, the reward would be $62,500. The [rewards page](/rewards) explains every payment condition.

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

Before sending the draft to the underwriting leader, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) so the disclosure matches your agreement.

## Sources

- https://content.naic.org/glossary-insurance-terms
- https://docs.guidewire.com/cloud/pc/202411/cloudapibf/cloudAPI/topics/122-PCjobTypes/03-policy-changes/c_initiating_a_policy_change.html
- 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
