Nine Million Objects Into 3DEXPERIENCE Across Multiple Sites, on a Two-Day Go-Live Window
SmarTeam V5, SOLIDWORKS ePDM and a third legacy system migrated to 3DEXPERIENCE 2015x in a two-step, multi-site programme built on SteepGraph’s Data Migration Framework.
A Denmark-based industrial equipment manufacturer operating across multiple sites
At a glance
- Industry
- Industrial equipment manufacturing
- Region
- Denmark
- Size
- 5,000–10,000 employees
- Platform
- 3DEXPERIENCE
- Our role
- End-to-end responsibility through go-live, and support
Results
8,996,611
objects, relationships and files migrated
Go-live delivered inside a 2–3 day window
The challenge and what we did
The challenge
- Diverse data types — SOLIDWORKS, AutoCAD, Inventor and ME10 data, scanned PDFs, and non-CAD data such as Office documents.
- A migration data size of 8,996,611 objects, relationships and files, with the storage, transfer and processing that implies.
- A two-step migration executed across multiple sites, with the coordination and synchronisation that required.
- Poor source data quality — missing attributes, duplicate records and unsupported characters.
What we did
- Extracted the data structure from the source system, including relationships and dependencies, to drive mapping and transformation.
- Applied a selective migration strategy, transferring only the latest released and initial non-released data.
- Used SteepGraph’s own Data Migration Framework to automate the migration process.
- Managed a strict two-to-three-day go-live window through detailed planning, coordination and execution.
- Used a delta migration to transfer only the changes made since the previous run, minimising downtime.
What we found
Three source systems fed this migration, and the data in them was not uniform: SOLIDWORKS, AutoCAD, Inventor and ME10 files sat alongside scanned PDFs and ordinary Office documents. The volume came to 8,996,611 objects, relationships and files. The estate was spread across multiple sites, which meant the migration had to be run in two steps and coordinated between them, and the source data carried the usual legacy problems — missing attributes, duplicate records and characters the target system would not accept.
What we built
The structure was extracted from the source first, relationships and dependencies included, so that mapping and transformation had something reliable to work against. Rather than move everything, a selective strategy carried only the latest released data plus the initial non-released data. SteepGraph’s Data Migration Framework automated the runs. The constraint that shaped the whole programme was the go-live window: two to three days, which left no room for a re-run, so the final cutover used a delta migration carrying only what had changed since the previous pass.
Filed under
- Industrial Machinery
- 3DEXPERIENCE
- Data Migration
- Engineering Data Management
- Change Management
- Data Migration Framework
- SmarTeam
- SOLIDWORKS ePDM
- EBOM
More customer stories
Machinery Manufacturing · 3DEXPERIENCE
From Designer Central to POWER’BY UPS, Without Stopping Operations
MTorres
3DEXPERIENCE upgraded from 2017x to 2021x, then CATIA V5 data migrated from Designer Central to POWER’BY (UPS), with SmarTeam data migrated on demand.
Industrial Equipment · 3DEXPERIENCE
Two Million CAD Objects Upgraded Over a Single Weekend
A German industrial equipment manufacturer
3DEXPERIENCE upgraded from 2015x to 2018x, with the full CAD migration parallelised across multiple machines and completed inside one weekend.
Aerospace · 3DEXPERIENCE
An Upgrade and a Move to Azure, Executed in Three Days
A UAE-based aerospace manufacturer
3DEXPERIENCE upgraded from 2017x to 2021x and migrated from on-premises to an Azure private cloud, with the de-customisation the new version required.
Behind this story.
The services and products this project used, and an expert to talk to about yours.
Talk to a 3DEXPERIENCE expert