This timeline is part of engineering change order process records. How integrators raise the topic without overstepping is in the PLM migration consultant guide. This page shows when each record class is at risk.
The migration timeline, milestone by milestone (Illustrative)
An invented plan for a fictional 600-person maker of packaging machinery replacing a legacy PLM system. Every date is an example; the real milestones are in the company's project plan.
| Milestone | When | Decision made | Records at risk | Who approves keeping them |
|---|---|---|---|---|
| Scoping and data mapping | Month 0 to 3 | Which object types and states migrate | Closed changes, past effectivities | Project sponsor with engineering operations |
| Trial loads | Month 4 to 6 | Which attributes map, which are dropped | Free-text fields holding Jira keys | Configuration manager |
| Cutover | Month 7 | New integration to the ERP goes live | Old integration log and message history | IT with engineering operations |
| Legacy read-only | Month 8 to 18 | Who keeps access, and for how long | Everything not migrated | CIO or IT director under policy |
| Legacy retired | Month 18 or later | Archive, export or delete | Whatever was not archived | Executive sponsor and counsel |
Most of the risk is decided early. By the time the legacy system is switched off, the scoping choices made in the first three months have already set what survives.
How long each record class tends to be kept
Retention is set by the company's policy and its contracts, and the migration plan often sets it in practice. This table shows the usual driver for each class.
| Record class | Typical home | What usually sets its life | Question to ask |
|---|---|---|---|
| Released current-state parts and BOMs | PLM | Migrated by default | Not usually at risk |
| Closed change requests and notices | PLM | Migration scope | Do closed changes move with their affected items? |
| Past effectivities | PLM and ERP | Migration scope and ERP history settings | Does the new platform keep effectivities no longer in force? |
| Requirement issues | Jira | Jira retention and project archiving | Are old projects archived or deleted? |
| ERP BOM change history | ERP | ERP retention policy | Are pre-change BOM states kept for closed orders? |
| Integration messages | Middleware logs | Log retention, often short | Is the old interface log kept after cutover? |
| Scanned pre-PLM change forms | File shares | Records policy | Are they indexed by change number? |
| Records on government contracts | All of the above | Contract clauses and federal rules | Do any contracts set a retention period? |
Effectivity history is the subtle one. PTC defines effectivity as the planned date, lot or serial number at which old versions are replaced by new ones in production. A migration that loads only effectivities still in force loses the record of when past changes cut in. In a standard SAP model, a BOM changed under a change number keeps a pre-change state ending at the valid-from date and a post-change state starting there, so the ERP may hold the other half of the story if its history is retained. For federal contractors, FAR 4.703(a) generally requires records to be available for 3 years after final payment, a contract clause can require longer, and electronic records may not be deleted or overwritten during that period.
What disappears first
Integration logs. The message that carried a change number from PLM to ERP often lives only in middleware logs with short retention. When the old interface is switched off, the evidence of how and when effectivity reached the ERP can go with it.
Keys in free-text fields. A Jira issue key typed into a change request's description may not map to any field in the new system and gets dropped in trial loads.
Renumbered identifiers. If change numbers or BOM versions are renumbered on load, every link that used the old number breaks.
Large Jira histories exported in a hurry. Atlassian documents that Jira Cloud CSV export handles up to 10,000 work items at a time, so larger histories come out in batches. A one-off export taken under deadline pressure can miss batches or comments.
Scanned forms and released current-state data tend to survive. That leaves the parts and the paper without the links between them, and the system map shows those links are what connect a decision to its outcome.
Who must approve keeping it
Never the partner. In a manufacturer of this size:
- Project sponsor and head of engineering operations: migration scope for change objects and effectivities.
- Configuration manager: attribute mapping, including where cross-system keys land.
- IT or CIO: integration logs, legacy access and archive options.
- Counsel: anything under customer contracts, export controls or a legal hold.
- CEO, COO or owner: whether any archived history is discussed with SourceX at all.
If no retention date is documented, there is no deadline to mention, and nothing should be kept beyond the company's own policy. The system modernization guide covers the timing conversation, and the legacy code modernization page covers a similar migration problem for software.
What a partner writes down
Record classes, years covered, the system and owner of each, which keys the migration keeps, and the documented read-only and retirement dates. Never drawings, BOMs, part numbers or exports. The company needs 50+ full-time employees at peak (contractors excluded), 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. What stays unknown until SourceX reviews it: which records customer agreements and export controls allow, and whether any buyer wants them. Similar inventories apply to QA and QC records, and the page on change-in-law clauses covers a later contract question.
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 a manufacturer can tell you which change history its migration keeps and when the legacy system goes read-only, register as a partner, confirm the company on who qualifies and read the program terms before introducing its decision-maker.