Preserving engineering change history through a PLM migration: a retention timeline from mapping to retirement

Short answer

Before a PLM modernization, inventory the engineering change history the migration might leave behind. That means closed change requests and notices, past effectivities, the cross-system keys that tie Jira issues and ERP BOM versions to each change, the old PLM-to-ERP integration log, and scanned pre-PLM change forms. Past effectivities and integration logs usually go first, at data mapping and cutover. Note the owner of each class and the documented date the legacy system goes read-only, and leave the decision to keep anything to the company.

Visual briefFull-size diagram
A migration timeline with four milestones, data mapping, cutover, legacy read-only and legacy retired; record chips for past effectivities and closed changes sit at data mapping, the interface log at cutover and unmigrated history at read-only, while an archive kept with company approval runs past retirement.
Illustrative migration plan. Real milestones come from the company's own project plan and retention policy.

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.

MilestoneWhenDecision madeRecords at riskWho approves keeping them
Scoping and data mappingMonth 0 to 3Which object types and states migrateClosed changes, past effectivitiesProject sponsor with engineering operations
Trial loadsMonth 4 to 6Which attributes map, which are droppedFree-text fields holding Jira keysConfiguration manager
CutoverMonth 7New integration to the ERP goes liveOld integration log and message historyIT with engineering operations
Legacy read-onlyMonth 8 to 18Who keeps access, and for how longEverything not migratedCIO or IT director under policy
Legacy retiredMonth 18 or laterArchive, export or deleteWhatever was not archivedExecutive 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 classTypical homeWhat usually sets its lifeQuestion to ask
Released current-state parts and BOMsPLMMigrated by defaultNot usually at risk
Closed change requests and noticesPLMMigration scopeDo closed changes move with their affected items?
Past effectivitiesPLM and ERPMigration scope and ERP history settingsDoes the new platform keep effectivities no longer in force?
Requirement issuesJiraJira retention and project archivingAre old projects archived or deleted?
ERP BOM change historyERPERP retention policyAre pre-change BOM states kept for closed orders?
Integration messagesMiddleware logsLog retention, often shortIs the old interface log kept after cutover?
Scanned pre-PLM change formsFile sharesRecords policyAre they indexed by change number?
Records on government contractsAll of the aboveContract clauses and federal rulesDo 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.

  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

Should a PLM integrator recommend migrating all change history?

Not on SourceX's account. What moves is a scoping decision for the company and its project sponsor, under its retention policy. A partner can ask what is in scope and note the answer, nothing more.

Is a PLM go-live date a deadline for an introduction?

Only when it is written down in the project plan and changes access to history, such as a date when the legacy system goes read-only. Without a documented date there is no deadline to mention.

What if the company has already retired its old PLM?

Ask what was kept: an archive database, PDF exports or nothing. Partial history is still worth describing accurately, and SourceX decides fit after its own review.

Sources

  1. support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_…
  2. help.sap.com/docs/SAP_S4HANA_ON-PREMISE/18ee18df146f46e9a…
  3. support.atlassian.com/jira/kb/export-over-10-000-work-items-in-jir…
  4. acquisition.gov/far/4.703
  5. refer.sourcex.si/terms

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