Engineering system modernization archive context checklist: what to confirm before the legacy system goes dark

Short answer

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.

Visual briefFull-size diagram
A countdown timeline with three milestones, announcement, cutover and switch-off of the old PLM link, where checklist items tick off one by one before the final milestone closes.
The checklist on a countdown. Milestone dates are the company's own; this page sets none.

This checklist is part of the PLM partner guide to change-to-order trails. 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.

MilestoneWhat it means for the trailTypical owner of the date
AnnouncementScope is still open; adding a history item costs a line in the planProgram sponsor or COO
CutoverThe new integration starts carrying releases; the old one stops receiving new onesEngineering systems lead and ERP lead
Switch-offThe legacy system, its integration and sometimes old shop-floor records stop being readableIT 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.

ConfirmWho owns itIf skipped
Whether closed work orders and their history are in migration scope, or stay in the old ERPERP leadNobody 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 severalEngineering systems leadThe 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 recordsEngineering systems administratorChange reasoning survives as a final state with no sequence
Who owns the designs: the company, its customers, or both, and whether export controls applyOwner and counselLater 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.

ConfirmWho owns itIf skipped
Whether each historical work order records the revision it builtPlannerPast orders can be matched to items but not to changes
Whether rework, use-as-is and scrap transactions carry the change numberShop-floor systems administrator or ERP leadThe 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 publishedIntegration leadThe history of past releases disappears with the old middleware
A count, in ranges, of years of change history and work ordersEngineering systems lead and ERP leadNobody can judge scale when the owner asks
Whether the owner has heard about the licensing option and who would decidePartner, with the ownerThe 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.

ConfirmWho owns itIf skipped
The switch-off date and whether a read-only archive of the old PLM will existIT managerThe 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 whenERP leadThe 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 handEngineering systems leadThe trail exists only as two disconnected archives
Whether the owner's decision about an introduction is recorded: introduce, revisit, or stopPartner, with the ownerThe question goes unanswered and closes by default

If the client is also closing a plant or a product line, the manufacturing plant closure page covers the extra records questions that raises. For code rather than engineering records, legacy code modernization data 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.

ItemStatus at switch-offResult for the trail
Revision stamped on ordersConfirmed before announcement; closed orders archived read-onlyOrders from 2013 onward still match their revision
Scrap transactions linked to change numbersSkipped; scrap carried only a reason code, and the old integration log was deleted at switch-offScrap decisions from before cutover can no longer be tied to a change
Ownership of designsConfirmed: two product lines build-to-print for a customerThose lines are flagged out of any licensing discussion
Owner's decisionRecorded: introduce, COO as working contactIntroduction 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 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 explains. To have the owner conversation itself, use the engineering system modernization meeting agenda; the 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, confirm fit on who qualifies, and keep the program terms at hand.

  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

Does SourceX set a deadline for any of these milestones?

No. Every date on this checklist belongs to the company: its announcement, its cutover window, its license end for the old PLM. If a milestone has already passed, record what was kept and what was not.

Who should own the checklist on the client side?

Usually the engineering systems lead keeps it, with the production planner and ERP lead answering their rows. The owner signs off only on the rows about rights and the introduction decision.

Is a read-only copy of the old PLM enough?

It keeps the engineering half. Whether the trail survives depends on the production half too: closed orders, their revision stamps and their dispositions, which often live in a different system with its own end date.

Sources

  1. refer.sourcex.si/terms
  2. learn.microsoft.com/en-us/dynamics365/supply-chain/engineering-c…
  3. learn.microsoft.com/en-us/dynamics365/supply-chain/engineering-c…

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