# Dispatch platform change archive checklist | SourceX

Canonical: https://refer.sourcex.si/resources/dispatch-platform-change-archive-context-checklist
Last updated: 2026-11-05

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.

This page belongs to the [dispatch platform change guide for field service integrators](/guides/moment-dispatch-platform-change-field-service-integrators). The [timed owner conversation](/resources/dispatch-platform-change-meeting-agenda) gets the first answers on record; this checklist keeps them honest as go-live approaches.

## The five links in a repeat-visit chain

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.

| Link | What it records | Typical way it breaks |
|---|---|---|
| First diagnosis | The opening theory and the part fitted | Replaced when the next visit is logged |
| Callback link | Proof that a later job was a return trip | Logged as a fresh, unconnected job |
| Revised diagnosis | The corrected theory | Held only in notes or photos left out of scope |
| Resolution | The fix that worked, with measurements | Measurements never mapped across |
| Verification | Evidence the repair held | Visible 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.

| Confirm | Owner | If skipped |
|---|---|---|
| How many years of closed work orders the old system holds, and for which service lines | Platform admin | The archive scope is set without knowing what exists |
| Whether each visit keeps its own dated diagnosis entry | Service operations manager | The team discovers after cutover that only the last value survived |
| Whether callbacks carry a parent link or flag | Service operations manager | Repeat visits become unrelated jobs in any export |
| Who owns service records, and whether OEM, warranty or customer contracts limit reuse | Owner or counsel | Rights 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.

| Confirm | Owner | If skipped |
|---|---|---|
| Closed history is either imported with notes and attachments or archived whole | Integrator lead | A flat export keeps headers and drops the reasoning |
| Problem, incident and resolution codes are mapped from old to new, in writing | Service operations manager | Old codes cannot be read once the new code list goes live |
| Test readings and inspection results are in scope, not just the close status | Platform admin | Verification evidence is lost even though jobs show as completed |
| Status history is kept, not just the final status | Platform admin | Jobs 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.

| Confirm | Owner | If skipped |
|---|---|---|
| The date and trigger for retiring the old system: contract end, hosting, server | Owner or IT | History disappears at a renewal nobody linked to it |
| Where the archive will live and who can read it | IT or operations | The archive exists but nobody can open it |
| Someone who knows the old field meanings is named and reachable | Service operations manager | The archive is readable but not interpretable |
| Who can authorize a licensing discussion about the archive | CEO (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.

| Link | State | Note |
|---|---|---|
| First diagnosis | Confirmed | Separate dated entry per visit since 2016 |
| Callback link | Partial | Flag used since 2019; earlier callbacks unlinked |
| Revised diagnosis | Confirmed | In visit notes, included in archive scope |
| Resolution and readings | Partial | Readings captured on mobile forms since 2020 |
| Verification | Unknown | Company to confirm its own callback window |
| Ownership | Partial | One 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](/resources/dispatch-platform-change-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](/rewards).

Companies like this cluster in [industrial services](/industries/industrial-services-private-equity), [route-based services](/industries/route-based-services-private-equity) and [fire and life safety roll-ups](/guides/fire-and-life-safety-roll-up). The guide to [assessing field service records and resolution notes](/guides/how-to-assess-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](/register), check [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce them.

## Sources

- https://learn.microsoft.com/en-us/dynamics365/field-service/work-order-resolutions
- https://learn.microsoft.com/en-us/dynamics365/field-service/incident-type-overview
- https://learn.microsoft.com/en-us/dynamics365/field-service/work-order-status-booking-status
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
