# Policy system migration and endorsement history | SourceX

Canonical: https://refer.sourcex.si/guides/moment-policy-system-migration-insurance-software-consultants
Last updated: 2026-11-04

Sometimes, but a policy system migration is when you find out. In a well-run legacy system, each policy version (the original bind, each endorsement, each renewal) sits beside the referral note, rating change or coverage decision that caused it. Some migration plans convert only the current term and archive the rest, which can separate the versions from the decisions. Ask the authorized owner whether those links exist and survive cutover. If the company is eligible and interested, introduce its decision-maker to SourceX.

## Are the relevant policy versions linked to operational decisions?

That is the qualifying question, and it is narrower than "do you have policy data?" Almost every insurer, MGA and agency has policy data. Far fewer can show, for a given endorsement, why it was issued, who approved it and what happened next.

An endorsement is, in the NAIC glossary's words, an amendment or rider to a policy adjusting the coverages and taking precedence over the general contract. NAIC consumer guidance adds that an endorsement becomes part of the legal insurance agreement and can be added at purchase, mid-term or at renewal. Each one is a decision point. A commercial policy that has run for six years may carry a dozen of them, and each was triggered by something: a new location, a loss, an underwriting referral, a broker request, a rate filing.

Policy administration systems record these as transactions. In Guidewire PolicyCenter's Cloud API, for example, a policy change is started with an effective date and creates a new job of type PolicyChange. Whether the reason for that change, and the referral note or approval behind it, is linked to the job depends on how the company configured and used its system.

### Why endorsement-aware decision histories are easy to overlook

Migration teams are measured on in-force accuracy: the right coverages, premiums and forms on day one in the new system. History is a storage question, and storage questions get answered with "archive it as PDFs".

A PDF of each policy version keeps what the policy said. It does not keep why it changed. The decision context usually sits elsewhere: underwriting worksheets, referral queues, rating overrides, broker emails attached to the account. When those are linked to the version in the legacy system, the company holds a record of judgment under real conditions. When the migration flattens them, that record becomes very hard to rebuild.

That is the useful thing an insurance software consultant knows that an owner may not: which links the migration design keeps and which it drops.

## The evidence asset: a version-to-decision map for one policy

Illustrative. A 260-person specialty MGA is moving from a legacy policy system to a cloud platform. One commercial property policy shows the pattern you are listening for.

| Version | Policy event | Decision that caused it | Linked record in legacy system | Kept by the migration plan? |
|---|---|---|---|---|
| v1 | New business bind | Underwriter accepted the risk after an inspection | Inspection report and referral approval | Yes, converted as account documents |
| v2 | Mid-term endorsement: second location added | Broker request; underwriter priced the new location | Rating worksheet and broker email | No, archived as a PDF |
| v3 | Mid-term endorsement: water damage sublimit reduced | Loss on the first location triggered a referral | Referral note linking the claim number | No, link to the claim dropped |
| v4 | Renewal with a new exclusion | Portfolio rule change after a rate review | Underwriting guideline version | Partly, guideline not versioned |

The question to the owner is about the fourth column, not the second. If the answer is "yes, those are linked, and we can keep them readable", the company may hold endorsement-aware decision histories. If the answer is "the policy documents are archived", it probably does not, and an introduction is less useful. The [underwriting notes data type page](/data-types/underwriting-notes-ai-training) explains why the reasoning beside a policy matters more than the policy itself.

## Which four metadata questions follow the opener?

If the owner says the versions are linked, four follow-ups tell you whether the record set is worth describing to SourceX. None of them requires seeing a policy.

1. **Which lines and years carry linked decisions?** A carrier may have clean links for commercial property since a 2019 upgrade and none for older personal lines. Note the range the owner gives, not a guess.
2. **Where does the decision context live?** Referral queues, rating overrides and underwriting worksheets may sit inside the policy system, in a document store keyed to the policy number, or in email. Linked by policy and version number is strong; "somewhere in the shared drive" is weak.
3. **What does the conversion design keep readable after cutover?** Ask whether history is converted, archived in a queryable read-only store, or reduced to PDFs, and when the legacy system is switched off.
4. **Who owns the records and can authorize a licensing discussion?** For an MGA, the CEO (often the owner) authorizes it, but carrier agreements may limit reuse of underwriting files, so general counsel matters too. For a carrier, it is the CEO, with the chief underwriting officer and legal advising.

## Does the company qualify, and what stays unknown?

Check [who qualifies](/who-qualifies) first. The introduced 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.

What you can know at metadata level: the system, the lines and years covered, whether versions link to decisions, which agreements might restrict reuse, and who can authorize a discussion. What stays unknown until SourceX reviews it: demand for these records, the rights review result, the de-identification scope, any offer, and any reward. You never request or handle policy files yourself.

### Reward disclosure and owner permission

Sign the Channel Partner Agreement before submitting an introduction, and introduce only with the decision-maker's agreement. Credit goes to the first valid introduction within the 90-day window, recorded when the company submits a verified application; one partner per company. The default reward on a company's first qualifying transaction is 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%. Illustrative arithmetic only: a $40,000 payout to the company is below the USD 100,000 Minimum Transaction, so it would earn no reward unless SourceX agreed in writing; a $400,000 payout for a qualifying completed handoff would mean a $70,000 reward (USD 50,000 plus 5%). 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. See the [rewards page](/rewards) for the payment statuses. For other clients facing a similar event, try the [network opportunity finder](/tools/network-opportunity-finder), and browse partner playbooks under [/for](/for), including the [data migration consultant](/for/data-migration-consultant) page and the [insurance industry overview](/industries/insurance).

The introduction itself can be short: the migration date, the lines and years with linked decision history the owner described, one sentence on SourceX licensing approved operating records directly from companies, and the disclosure that you may receive a reward SourceX pays separately, so it does not reduce the company's payout.

## Go deeper on policy system migrations

- [Policy system migration introduction email](/resources/policy-system-migration-introduction-email): a template for introducing the decision-maker before cutover, with the disclosure built in.
- [Policy system migration meeting agenda](/resources/policy-system-migration-meeting-agenda): a timed agenda for the first owner conversation about endorsement history.
- [Policy system migration archive context checklist](/resources/policy-system-migration-archive-context-checklist): a checklist of conversion, retention and authority facts to confirm before the legacy system goes dark.

## 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 owner confirms that versions link to decisions and wants to talk before cutover, [register as a partner](/register), check the company on [who qualifies](/who-qualifies), and read the [program terms](/terms) before you make the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
- https://content.naic.org/glossary-insurance-terms
- https://content.naic.org/article/what-you-need-know-about-adding-endorsement-or-rider-existing-insurance-policy
- https://docs.guidewire.com/cloud/pc/202411/cloudapibf/cloudAPI/topics/122-PCjobTypes/03-policy-changes/c_initiating_a_policy_change.html
