Policy system migration archive context checklist: what to confirm before the legacy system goes dark

Short answer

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.

Visual briefFull-size diagram
A vertical countdown with three milestones, announcement, go-live cutover and final shutdown, where checklist items about version links, attachment keys and read-only access tick off one by one before the legacy policy system is turned off.
The checklist as a countdown. Milestones follow the company's documented migration dates; none are assumed.

This checklist is part of the policy system migration guide. Most answers come out of the 30-minute 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.

MilestoneWhat it usually isWho sets itIf no date exists
AnnouncementBoard or steering approval of the replacement platformCIO or COOUse the approval meeting once it is scheduled
Go-live cutoverThe day in-force business starts running on the new platformProject directorLeave blank and ask who will set it
Final shutdownThe day the old platform can no longer be readCIO with financeMark 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.

ConfirmOwnerIf skipped
Which lines and years carry reasons beside each term and amendmentHead of underwritingThe design treats all history as equal and stores it flat
Whether reasons and approvers are structured fields or free textBusiness analyst for the old platformNobody knows whether the link can be searched until it is too late to keep
Which treaties or fronting deals may limit reuse of risk filesGeneral counselRights questions surface after history is already reduced to PDFs
Who could authorize a licensing discussionCEOA 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.

ConfirmOwnerIf skipped
Whether prior terms are converted, archived queryably or rendered as documentsMigration program managerVersion history survives but loses its structure
Whether attachments keep their policy and version keys in the archiveData conversion leadWorksheets and referral notes detach from the endorsement they explain
Whether transaction types and reason codes are mapped or droppedPolicy admin lead"Why it changed" collapses into "it changed"
Whether broker emails filed to accounts move with themAgency or distribution operationsRequest 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.

ConfirmOwnerIf skipped
The documented switch-off date and any read-only periodCIOThe history disappears without anyone deciding it should
Where the read-only archive lives and who can query itInfrastructure leadThe archive exists but no one can describe it
The retention rule that applies to the archiveRecords manager or complianceOld terms are purged on schedule before anyone asks
Whether the owner wants an introduction to SourceX before switch-offOwnerThe 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.

MilestoneItemStatusNote recorded
AnnouncementLines with reasons attachedDoneFarmowners from 2016; small business scanned files only
AnnouncementReinsurance treaty limits on reuseOpenCounsel reading the treaty wording
Go-live cutoverWorksheet keys survive archivingAt riskMapping keeps account number, loses term sequence
Go-live cutoverChange reasons translatedDoneOld codes crosswalked to the new list
Final shutdownMainframe read-only windowDoneDocumented window after the final wave
Final shutdownOwner decisionPendingPresident 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 and the Jira Data Center to Cloud history page, and the email archive migration guide 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. 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, and the data migration consultant page 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, check the company on who qualifies and read the program terms first.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. 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.

Common questions

What if the carrier has not set a switch-off date for the legacy system?

Then the third milestone is open, and the item is to find out who decides it, usually the CIO with finance. Do not supply a date of your own; an assumed deadline adds pressure the company never agreed to.

Is the consultant responsible for preserving the history?

No. The carrier or MGA decides what to convert, archive or drop. The consultant asks the questions in time and writes down the answers at metadata level.

Does a complete checklist mean the company qualifies?

No. It describes what the company holds and who controls it. Eligibility, rights and any offer are decided only after the company applies and SourceX reviews it.

Sources

  1. content.naic.org/article/what-you-need-know-about-adding-endo…
  2. docs.guidewire.com/cloud/pc/202411/cloudapibf/cloudAPI/topics/1…
  3. refer.sourcex.si/terms
  4. refer.sourcex.si/rewards

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment