# Policy migration archive context checklist | SourceX

Canonical: https://refer.sourcex.si/resources/policy-system-migration-archive-context-checklist
Last updated: 2026-11-05

Work through three milestones in order: before the replacement is announced, before go-live on the new platform, and before the old platform is turned off for good. At each, confirm a few facts about whether policy versions stay linked to the decisions behind them, name the person who owns each item, and know what is lost if it is skipped. Use the insurer's own documented dates. Record answers only; never request policy files, pricing sheets or claim files.

This checklist is part of the [policy system migration guide](/guides/moment-policy-system-migration-insurance-software-consultants). Most answers come out of the [30-minute meeting agenda](/resources/policy-system-migration-meeting-agenda); this page keeps them from drifting as go-live approaches.

## Set the three dates first

A countdown only helps when the clock is real. Before ticking anything, write down each milestone as the company has documented it and who set it.

| Milestone | What it usually is | Who sets it | If no date exists |
|---|---|---|---|
| Announcement | Board or steering approval of the replacement platform | CIO or COO | Use the approval meeting once it is scheduled |
| Go-live cutover | The day in-force business starts running on the new platform | Project director | Leave blank and ask who will set it |
| Final shutdown | The day the old platform can no longer be read | CIO with finance | Mark open; ask who decides |

Many insurers go live in waves by line of business or state. If so, repeat the go-live milestone once per wave.

## Milestone 1: before the migration is announced

Once a replacement is public inside the insurer, scope hardens quickly. These items are cheapest to settle now.

| Confirm | Owner | If skipped |
|---|---|---|
| Which lines and years carry reasons beside each term and amendment | Head of underwriting | The design treats all history as equal and stores it flat |
| Whether reasons and approvers are structured fields or free text | Business analyst for the old platform | Nobody knows whether the link can be searched until it is too late to keep |
| Which treaties or fronting deals may limit reuse of risk files | General counsel | Rights questions surface after history is already reduced to PDFs |
| Who could authorize a licensing discussion | CEO | A later conversation has no clear decision-maker |

NAIC consumer guidance notes that a rider can be attached at the start of coverage, partway through a term or when coverage renews. A farm or small business account kept for a decade can therefore hold many such amendments, and this step is about knowing whether the reasons for them travel too.

## Milestone 2: before go-live cutover

The conversion design decides what becomes live data, what becomes archive and what is left behind. Ask while mapping is still open.

| Confirm | Owner | If skipped |
|---|---|---|
| Whether prior terms are converted, archived queryably or rendered as documents | Migration program manager | Version history survives but loses its structure |
| Whether attachments keep their policy and version keys in the archive | Data conversion lead | Worksheets and referral notes detach from the endorsement they explain |
| Whether transaction types and reason codes are mapped or dropped | Policy admin lead | "Why it changed" collapses into "it changed" |
| Whether broker emails filed to accounts move with them | Agency or distribution operations | Request context stays in a mailbox that is later deleted |

The new platform will record new changes its own way; in Guidewire PolicyCenter's Cloud API, for example, a policy change is started with an effective date and creates a job of type PolicyChange. That says nothing about how old transactions are carried over. The question here is only about the legacy history.

## Milestone 3: before final shutdown

After switch-off, whatever was not kept is gone or very costly to rebuild.

| Confirm | Owner | If skipped |
|---|---|---|
| The documented switch-off date and any read-only period | CIO | The history disappears without anyone deciding it should |
| Where the read-only archive lives and who can query it | Infrastructure lead | The archive exists but no one can describe it |
| The retention rule that applies to the archive | Records manager or compliance | Old terms are purged on schedule before anyone asks |
| Whether the owner wants an introduction to SourceX before switch-off | Owner | The decision is made by default rather than by the owner |

## Worked example: one insurer's countdown

Illustrative. A 520-person mutual insurer retiring a mainframe system that holds its farmowners and small business book.

| Milestone | Item | Status | Note recorded |
|---|---|---|---|
| Announcement | Lines with reasons attached | Done | Farmowners from 2016; small business scanned files only |
| Announcement | Reinsurance treaty limits on reuse | Open | Counsel reading the treaty wording |
| Go-live cutover | Worksheet keys survive archiving | At risk | Mapping keeps account number, loses term sequence |
| Go-live cutover | Change reasons translated | Done | Old codes crosswalked to the new list |
| Final shutdown | Mainframe read-only window | Done | Documented window after the final wave |
| Final shutdown | Owner decision | Pending | President wants the board's view first |

The "at risk" row is the one the consultant raises with the migration lead, as a conversion question in its own right; the referral is not the reason to change it. Comparable countdowns for other systems are on the [CRM migration handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-a-crm-migration) and the [Jira Data Center to Cloud history page](/systems/jira-data-center-to-cloud-migration-history), and the [email archive migration guide](/guides/email-archive-migration) covers the mailbox side.

## Who can authorize, and what stays unknown

- **Records:** lines, years and decision-context forms, as the company describes them.
- **Owner:** the company, its carriers or program administrators, as counsel confirms.
- **Authority:** the CEO, named at milestone one.
- **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.

Unknown until SourceX reviews it: demand for endorsement decision histories, the rights result, de-identification scope, any offer and any reward. When the owner opts in, use the [introduction email](/resources/policy-system-migration-introduction-email). Sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application, one partner per company. SourceX pays any reward separately, never from the company's payout. Illustrative only: a USD 100,000 payout to the company for a qualifying completed handoff would mean a USD 55,000 reward on its first qualifying transaction, the greater of USD 50,000 plus 5% and 15%. See [rewards](/rewards), and the [data migration consultant page](/for/data-migration-consultant) for the wider partner play.

## 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 countdown shows linked history the owner wants to discuss before switch-off, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) first.

## Sources

- 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
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
