# Mistake
What Goes Wrong
Jaydu's Approach
Impact
Phase 1 — Before Migration
01. No file audit
Assumed scope
File count guessed from memory; sub-assemblies and linked drawings missed entirely
Automated crawl of all drives + PDM vaults; full dependency map before Day 1
Critical
02. No stakeholder alignment
Siloed scoping
Engineering scopes alone; IT and ERP find out about incompatibilities after kick-off
Joint session — engineering, IT, and ERP aligned before any work begins
Critical
03. No quality threshold
All files treated equal
Broken assemblies and blank metadata pushed through conversion unchanged
3-tier classification: direct convert / clean then convert / full rebuild
Critical
04. No BOM mapping
ERP ignored pre-project
BOM structure never mapped to ERP fields — mismatches found post go-live
BOM hierarchy mapped to ERP field structure before migration starts
Critical
Phase 2 — During Migration
05. No real pilot
2 files ≠ validated
Vendor runs 1–2 sample files and declares the process ready for full scale
500–2,000 file pilot covering every geometry type with a formal pass/fail matrix
Critical
06. No data freeze
Live edits during run
Engineers update legacy files mid-migration; completed batches get invalidated
PDM read-lock + ECO freeze applied per product line before each batch
Critical
07. No audit trail
Zero traceability
Failed files silently skipped; no log, no sign-off, no ERP reconciliation possible
Automated log: source path, status, timestamp + engineer sign-off gate per batch
Critical
08. Visual-only QA
Geometry errors missed
NURBS degradation, bend table loss, and GD&T stripping go undetected until manufacturing
Geometry diff engine + STEP AP242 PMI check + sheet metal K-factor validation
Critical
Phase 3 — After Go-Live
09. No go-live validation
"Visible = done"
Files appear in new PDM — project closed. BOM accuracy and file count never reconciled
100% file count reconciliation + BOM delta report vs. ERP master before sign-off
High
10. No post-live review
Support ends at launch
Geometry errors and BOM gaps surface in production weeks later with no review process
30/60/90-day structured reviews are contractual deliverables — not optional extras
High
11. Wrong vendor
Price over capability
Single-platform vendor, no US references, post-live support quoted separately and skipped
Multi-platform (CATIA·NX·SolidWorks·STEP·JT) + 90-day hypercare in every engagement
High
