# Engineering modernization archive checklist | SourceX

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

Confirm a short list of facts at three moments: before the program is announced, before cutover, and before the legacy engineering system and its ERP integration are switched off. At each moment the list names what to confirm, who on the client side owns the answer, and what is lost if the item is skipped. The aim is one: that the company decides, while the trail still exists, whether engineering changes can still be traced to the production orders they affected.

This checklist is part of the [PLM partner guide to change-to-order trails](/guides/moment-engineering-system-modernization-plm-partners). It sets no dates of its own: every milestone below is the company's verified event, taken from its own project plan or license terms.

## Three milestones, one countdown

Upgrade programs run on their own calendar, and the history question has to fit inside it. Three milestones matter, because each closes off a different kind of fix.

| Milestone | What it means for the trail | Typical owner of the date |
|---|---|---|
| Announcement | Scope is still open; adding a history item costs a line in the plan | Program sponsor or COO |
| Cutover | The new integration starts carrying releases; the old one stops receiving new ones | Engineering systems lead and ERP lead |
| Switch-off | The legacy system, its integration and sometimes old shop-floor records stop being readable | IT manager, often tied to a license end date |

After switch-off, a lost link can only be rebuilt by hand, if at all. Ask for the three dates early and write them on the checklist exactly as the company gives them.

## Before the program is announced

At this point the trail is intact, and the job is to make sure the program scope does not quietly exclude it.

| Confirm | Who owns it | If skipped |
|---|---|---|
| Whether closed work orders and their history are in migration scope, or stay in the old ERP | ERP lead | Nobody plans for the shop-floor half of the trail |
| Where effective dates live today: a field on the change, an ERP engineering version with dates, a spreadsheet, or several | Engineering systems lead | The new platform is designed without knowing which history needs carrying |
| Whether historical change objects (ECR, ECO, ECN) migrate with their status history or only as current records | Engineering systems administrator | Change reasoning survives as a final state with no sequence |
| Who owns the designs: the company, its customers, or both, and whether export controls apply | Owner and counsel | Later rights questions surface after decisions are already made |

The documented Microsoft model is a useful prompt for the second row. In Dynamics 365 Supply Chain Management, engineering versions carry effective-from and effective-to dates, and a category can enforce contiguous effectivity or allow overlaps. Ask which pattern the client's current system follows; do not assume it.

## Before cutover

Cutover is when the old integration stops carrying new releases. The questions here are about the join between the two systems, because that join is what no workstream owns.

| Confirm | Who owns it | If skipped |
|---|---|---|
| Whether each historical work order records the revision it built | Planner | Past orders can be matched to items but not to changes |
| Whether rework, use-as-is and scrap transactions carry the change number | Shop-floor systems administrator or ERP lead | The most informative orders lose their link first |
| Whether the new integration will be rebuilt forward only, or also preserve the record of what the old one published | Integration lead | The history of past releases disappears with the old middleware |
| A count, in ranges, of years of change history and work orders | Engineering systems lead and ERP lead | Nobody can judge scale when the owner asks |
| Whether the owner has heard about the licensing option and who would decide | Partner, with the owner | The decision gets made by default when the old system retires |

Dispositions deserve the most care. In Dynamics 365, a change request can be checked against open production orders, which can be blocked or notified, and the notification is marked resolved once the orders are canceled or modified. That kind of record shows an engineering decision meeting live production. If the client's equivalent sits only in the old integration's logs, cutover is the last point to note where it lives.

## Before the old PLM and integration are switched off

Switch-off is the real deadline, and it is set by the company, usually by a license end, a server retirement or a hosting contract. The questions now are about what remains readable afterward.

| Confirm | Who owns it | If skipped |
|---|---|---|
| The switch-off date and whether a read-only archive of the old PLM will exist | IT manager | The engineering half of the trail may vanish without anyone choosing that |
| Whether closed production orders remain readable in the old ERP or an archive, and until when | ERP lead | The production half ends on a different date from the engineering half |
| Whether the change number to order number join can still be queried, or only reconstructed by hand | Engineering systems lead | The trail exists only as two disconnected archives |
| Whether the owner's decision about an introduction is recorded: introduce, revisit, or stop | Partner, with the owner | The question goes unanswered and closes by default |

If the client is also closing a plant or a product line, the [manufacturing plant closure page](/industries/manufacturing-plant-closure) covers the extra records questions that raises. For code rather than engineering records, [legacy code modernization data](/data-types/legacy-code-modernization-data-ai) describes a parallel case.

## Illustrative: one row skipped, one row kept

Illustrative. A 450-person maker of conveyor systems is moving from an on-premises PLM to a cloud platform.

| Item | Status at switch-off | Result for the trail |
|---|---|---|
| Revision stamped on orders | Confirmed before announcement; closed orders archived read-only | Orders from 2013 onward still match their revision |
| Scrap transactions linked to change numbers | Skipped; scrap carried only a reason code, and the old integration log was deleted at switch-off | Scrap decisions from before cutover can no longer be tied to a change |
| Ownership of designs | Confirmed: two product lines build-to-print for a customer | Those lines are flagged out of any licensing discussion |
| Owner's decision | Recorded: introduce, COO as working contact | Introduction made before switch-off |

The trail survived in part. That is a normal outcome, and the checklist made it a decision rather than an accident.

## Who can authorize the next step, and what stays unknown

The company normally owns its change history and production records, subject to customer-owned designs and export-controlled data, which its counsel judges. The person who can open a licensing discussion is the CEO; in an owner-run manufacturer, that is usually the owner.

Before introducing anyone, check 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. The [engineering and design screening worksheet](/resources/a-referral-screening-worksheet-for-engineering-and-design-businesses) helps with size and rights.

Partners stay at metadata level throughout: systems, years, ranges, owners. Never request drawings, BOM extracts or order samples. What stays unknown until SourceX reviews it: whether buyers want this trail, the rights review result, de-identification needs and any offer. Sign the Channel Partner Agreement before submitting; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. Illustrative only: a $400,000 payout to the company would mean a $70,000 reward, as the [rewards page](/rewards) explains. To have the owner conversation itself, use the [engineering system modernization meeting agenda](/resources/engineering-system-modernization-meeting-agenda); the [engineering change order process](/data-types/engineering-change-order-process) page explains the change records involved.

## 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 change-to-order trail still readable and the owner chooses an introduction before switch-off, [register as a partner](/register), confirm fit on [who qualifies](/who-qualifies), and keep the [program terms](/terms) at hand.

## Sources

- https://refer.sourcex.si/terms
- https://learn.microsoft.com/en-us/dynamics365/supply-chain/engineering-change-management/engineering-change-management
- https://learn.microsoft.com/en-us/dynamics365/supply-chain/engineering-change-management/engineering-versions-product-category
