Dispatch platform change archive context checklist: repeat-visit history to confirm before the legacy system is retired

Short answer

They do only if the migration keeps each visit's dated diagnosis, the callback link and the readings that proved the fix, and nobody can assume that. Confirm twelve items at three points: before the switch is announced, before go-live, and before the legacy system goes dark. Every item protects one link in the chain that shows a repair was attempted, revisited and proven, and every item has a named person who confirms it and a stated consequence if it slips. The company supplies the dates; nothing is exported to answer the list.

Visual briefFull-size diagram
A vertical countdown from announcement to cutover to legacy shutdown, with checklist items for diagnosis revisions, callback links, attachments and verification ticking off at each milestone.
The checklist as a countdown. Milestones use the company's documented dates; none are assumed.

This page belongs to the dispatch platform change guide for field service integrators. The timed owner conversation gets the first answers on record; this checklist keeps them honest as go-live approaches.

Every item below protects one of five links. Lose any one and the archive still proves a job happened, but no longer shows how the technicians' thinking changed or whether the second attempt worked.

LinkWhat it recordsTypical way it breaks
First diagnosisThe opening theory and the part fittedReplaced when the next visit is logged
Callback linkProof that a later job was a return tripLogged as a fresh, unconnected job
Revised diagnosisThe corrected theoryHeld only in notes or photos left out of scope
ResolutionThe fix that worked, with measurementsMeasurements never mapped across
VerificationEvidence the repair heldVisible only by querying old history for silence

Products structure these links in their own ways; Microsoft's Field Service, for instance, keeps several possible resolutions per incident type. Treat the five links as questions for whatever platform the client runs.

Countdown point one: before the change is announced

Asking now sounds like routine scoping, because nobody has yet decided what happens to closed history.

ConfirmOwnerIf skipped
How many years of closed work orders the old system holds, and for which service linesPlatform adminThe archive scope is set without knowing what exists
Whether each visit keeps its own dated diagnosis entryService operations managerThe team discovers after cutover that only the last value survived
Whether callbacks carry a parent link or flagService operations managerRepeat visits become unrelated jobs in any export
Who owns service records, and whether OEM, warranty or customer contracts limit reuseOwner or counselRights questions surface only after an introduction

Countdown point two: before cutover

Once the import is designed, closed jobs tend to be summarized into a status and a date. These items protect the detail.

ConfirmOwnerIf skipped
Closed history is either imported with notes and attachments or archived wholeIntegrator leadA flat export keeps headers and drops the reasoning
Problem, incident and resolution codes are mapped from old to new, in writingService operations managerOld codes cannot be read once the new code list goes live
Test readings and inspection results are in scope, not just the close statusPlatform adminVerification evidence is lost even though jobs show as completed
Status history is kept, not just the final statusPlatform adminJobs that were reopened for follow-up look as if they closed first time

The last row matters because status models differ. Dynamics 365 Field Service, for example, runs work orders through system statuses from Unscheduled to Posted and keeps booking statuses separate. Ask how the client's old tool recorded reopenings before you assume the final status tells the story.

Countdown point three: before the legacy system is retired

After shutdown, anything still open on this list may not be recoverable.

ConfirmOwnerIf skipped
The date and trigger for retiring the old system: contract end, hosting, serverOwner or ITHistory disappears at a renewal nobody linked to it
Where the archive will live and who can read itIT or operationsThe archive exists but nobody can open it
Someone who knows the old field meanings is named and reachableService operations managerThe archive is readable but not interpretable
Who can authorize a licensing discussion about the archiveCEO (in an owner-run company, the owner)An interested company has nobody able to say yes

Telematics and route data sometimes sit beside the dispatch tool. Record them as linked systems and leave their value to SourceX's review.

Example: a completed checklist read back to the owner

Illustrative. A fictional 190-person commercial refrigeration service company completed the checklist across all three milestones.

LinkStateNote
First diagnosisConfirmedSeparate dated entry per visit since 2016
Callback linkPartialFlag used since 2019; earlier callbacks unlinked
Revised diagnosisConfirmedIn visit notes, included in archive scope
Resolution and readingsPartialReadings captured on mobile forms since 2020
VerificationUnknownCompany to confirm its own callback window
OwnershipPartialOne grocery chain contract restricts reuse

That is a metadata-level description with no record opened. If the owner wants to go further, disclose, check fit and introduce.

Tell the owner you are a SourceX referral partner. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout. If a qualifying license completes and all payment conditions are met, SourceX may pay you a reward it funds separately; it is never deducted from the company's payout.

Fit: 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. Demand, the rights review and any offer remain unknown until SourceX reviews the application.

Sign the Channel Partner Agreement, then send the annotated introduction email to the authorized contact. 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. Illustrative only: a USD 100,000 Actual Supplier Payout on a company's first qualifying transaction would mean a USD 55,000 default reward, payable under the conditions on the rewards page.

Companies like this cluster in industrial services, route-based services and fire and life safety roll-ups. The guide to assessing field service records and resolution notes explains what makes the notes in links three and four useful.

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 checklist shows the repeat-visit chain survives retirement and the owner wants to explore it, register as a partner, check who qualifies and read the program terms before you introduce them.

  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

The company plans to keep the old system read-only for years. Is the checklist still needed?

Yes, though with less urgency. Read-only systems still lose their admin, their hosting contract or their last person who knows the fields. Milestone three then becomes 'who keeps it readable, and until when'.

Who should own each item, the integrator or the company?

The company. The integrator asks the question and records the answer with the name of the person who gave it. Owning the archive is project work only if the company contracts for it.

What if diagnoses were only ever written as free text?

Mark the structured-diagnosis item 'no' and check that notes are in the archive scope. Free-text notes that describe what was suspected and what was found can be the richer record.

Sources

  1. learn.microsoft.com/en-us/dynamics365/field-service/work-order-r…
  2. learn.microsoft.com/en-us/dynamics365/field-service/incident-typ…
  3. learn.microsoft.com/en-us/dynamics365/field-service/work-order-s…
  4. refer.sourcex.si/terms
  5. 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