PLATFORM-INDEPENDENT
Data Migration Framework
A proven migration framework across 30+ enterprise PLM migration programmes—with configurable automation, reusable accelerators, and a delivery methodology designed to reduce risk at every stage.
- 2B+ Records Migrated
- Extraction from 20+ Enterprise Systems
- ITAR & EAR Controlled Data
- Selective or Big Bang
- Product structurespreserved
- CAD ↔ EBOM ↔ MBOMreconciled
- Revision historypreserved
- Relationshipsvalidated
- Files & attachmentsverified
- Controlled accessenforced
Move the knowledge, not just the records.
THE REALITY OF PLM MIGRATION
Every Migration Has Its Own Rules
PLM migration is rarely about moving everything.
What should move?
- SelectiveOnly the products, parts and structures you need.
- Big BangThe complete set, moved in one transition.
What should be preserved?
- CAD ↔ EBOM ↔ MBOMDesign and both BOMs arrive still aligned.
- History & RevisionsFull revision history, or latest release only.
What should change?
- Data CorrectionMissing and invalid values fixed in flight.
- Revision TransformationSchemes adapted to the target’s rules.
- Relationship RepairBroken links rebuilt, missing ones created.
What does the target require?
- Target-System RulesChecked against rules the old system never had.
- Correct on the Way InFixed before the data reaches the target.
- Controlled AccessAuthorised personnel only, source and target.
Move what you need. Preserve what matters. Fix what needs fixing. Arrive ready for the new system.
BUILT FOR DIFFERENT MIGRATION SCENARIOS
One Framework. Multiple Platforms. Multiple Approaches.
Every migration starts somewhere different and ends somewhere different.
Source systems
Oracle PLM
SOLIDWORKS PDM
3DEXPERIENCE / ENOVIA
Teamcenter
Windchill
Pro/INTRALINK
Documentum
Autodesk Vault
SmarTeam- Legacy / Custom / Local
Data Migration Framework
Source Profiling
Schema, volumes, quality
Mapping Workbench
Object, attribute, lifecycle
Run Orchestration
Waves, retries, cutover
Four ways in
- API / Web Services
- Database
- Files / Reports
- Custom Extraction
- Extract
- Transform
- Validate
- Correct
- Load
- Reconcile
Data Quality Rules
Pre-load and post-load checks
Reconciliation Reports
Record-level counts and deltas
Delta & Incremental
Big-bang or phased cutover
Target platforms
3DEXPERIENCE- Other PLM Systems
The framework adapts to the migration—not the other way around.
IN THE PRODUCT
The Framework, Configured
Mappings are set up on screen or imported from Excel, and every extraction is measured.
| Name | Admin Type | Source Table | Id Where Clause | Sequence | Scope | Target Table |
|---|---|---|---|---|---|---|
| Part | type | Part | Id IS NOT NULL | 1 | extraction | Part |
| CAD Part | type | CAD Part | Id IS NOT NULL | 2 | extraction | CAD Part |
| CAD Drawing | type | CAD Drawing | Id IS NOT NULL | 3 | extraction | CAD Drawing |
| CAD Assembly | type | CAD Assembly | Id IS NOT NULL | 3 | extraction | CAD Assembly |
| Document | type | Document | Id IS NOT NULL | 4 | extraction | Document |
| Part BOM | relationship | Part BOM | Id IS NOT NULL | 5 | extraction | Part BOM |
| CAD Structure | relationship | CAD Structure | Id IS NOT NULL | 6 | extraction | CAD Structure |
| Type | Target | Source | SQL Name | Mapping Type | Data Type | Multi-value Separator |
|---|---|---|---|---|---|---|
| Part | Item Number | item_number | item_number | direct | string | |
| Part | Name | name | name | direct | string | |
| Part | Type | type | type | direct | string | |
| Part | Revision | major_rev | major_rev | direct | string |
| type | name | owner | source | revision | description | policy | vault |
|---|---|---|---|---|---|---|---|
| Part | 00000365 | design_eng | Aras | A | 00000365 Part to migrate the data | Part Policy | eService Production |
| Part | 00000369 | design_eng | Aras | A | 00000369 Part to migrate the data | Part Policy | eService Production |
| Part | 000002 | design_eng | Aras | A | Physical Part to migrate the data 000002 | Part Policy | eService Production |
VALIDATION AT EVERY STEP
Know What Moved—and What Didn’t
Loading successfully is not the same as migrating correctly.
Extract
Is the right data coming out?
Source records, required fields, relationships, files.
Transform
Did it change as expected?
Values, revisions, mappings, structures, relationships.
Load
Did the target accept it?
Target rules, required values, object creation, links.
Reconcile
Does it match what we expected?
Source against target—records, structures, files, exceptions.
| Rule Status | Name | Description |
|---|---|---|
| Status not yet run | DateFormatCheck | No Input Parameters |
| Status not yet run | DuplicateTNRCheck | No Input Parameters |
| Status not yet run | RelationshipReplaceFromTo | Input Parameter Example:{name:"REL_SW_EXTERNAL_REFERENCE1",from:"TYP_S… |
| Status not yet run | SpecialCharacterCheck | No Input Parameters |
| Status not yet run | UpdateMajorMinorRevisionOnType | Input Parameter Example:{major:"TYP_STD_SW_COM_10406618901",minor:"TYP_ST… |
| Status not yet run | AutonumberGenerator | Input Parameter Example:{"types": [{"NAME": "TYPE_NAME","NUM_GEN_NAME": "NU… |
| Status not yet run | UpdatePathData | Input Parameter Example:{name:"I81_PATH_PAT_1261277731",from:"I81_TYP_REAL_… |
| Status not yet run | AssemblyConflictReport | No Input Parameters |
Correctness. Completeness. Relationships. Exceptions.
RESOURCES
Data Migration Framework in Action
Recorded sessions and the migrations behind them.
Webinars
All webinarsOn demand · 24 Sep 2024
Data Migration to 3DEXPERIENCE Platform – MTorres Success Story
On demand · 10 Sep 2025
Future-Proof Your Engineering: Migrate from SOLIDWORKS ePDM to 3DEXPERIENCE
On demand · 3 Jun 2025
Why Now is the Time to Transition from SmarTeam to the 3DEXPERIENCE Platform
On demand · 12 Mar 2025
Top 5 CAD BOM and EBOM Challenges and Solutions for 3DEXPERIENCE UPS Migration
Customer stories
All customer storiesSweden · High-tech
Windchill Product Analytics → 3DEXPERIENCE
14.76M records, one load window
Denmark · Industrial equipment, multi-site
SmarTeam · SOLIDWORKS ePDM · legacy → 3DEXPERIENCE
9M objects, relationships and files
Ireland · Electrical & electronics
ENOVIA → 3DEXPERIENCE 15x
Revisions sequences, stores and vaults intact
MTorres · Machinery manufacturing, Spain
Designer Central → POWER’BY (UPS)
10 months to migrate and test, operations never stopped
GET STARTED
Planning a PLM Migration?
Tell us the source system, the target platform, and what has to survive the move. We will tell you how the framework would approach it.
The service behind the framework
The framework is the tooling. The service is the team that runs it—ten phases from discovery to production cutover, reconciled at every one.
- Discovery
- Profiling
- Cleansing
- Mapping
- Transformation
- ETL Development
- Validation
- Reconciliation
- Dry Runs
- Production Cutover
FAQS
Questions We Get Asked
The Data Migration Framework is used as part of SteepGraph’s migration services, but it is designed for joint use by SteepGraph and customer teams. We can provide training so your team can work with the framework, review migration results, and handle supported corrections and changes.
Yes. The framework can support migrations between cloud PLM environments, including 3DEXPERIENCE Cloud, Aras Cloud, and other supported cloud PLM environments. The migration approach depends on the source and target systems and the type of data being migrated.
For migrations involving ITAR-controlled data, we can provide controlled access and use US-based SteepGraph personnel where required. Customer teams can also be trained to work with the framework within the agreed access and data-handling setup.
It helps reduce migration time, manual coding, complexity, and repeated cycles between business users and developers. More migration activities can be handled through configurable rules and corrections, making it easier to identify and resolve issues without rebuilding the migration for every change.