Windchill Data Migration

Get CAD data, documents and parts into Windchill from SolidWorks PDM, network folders or another PDM system, tested before it reaches production.

Data migration is the least glamorous part of a Windchill project and the part most likely to derail it. Tens of thousands of files, duplicate filenames, and parts that were edited on several machines all have to land in the right place. Fishbowl migrates with its own purpose-built tools, including LinkLoader, and with PTC's Windchill Bulk Migrator when that is the better fit. We can run the whole migration for you, or equip your team to run it.

What we migrate

CAD data

Creo, SolidWorks, AutoCAD and Autodesk Inventor files, bulk loaded into Windchill.

Documents and parts

Documents and WTParts are loaded alongside the CAD data they belong to.

From other PDM systems

SolidWorks PDM, Teamcenter and other third-party PDM systems, as well as plain network file folders.

Windchill to Windchill

Moving from an older Windchill system to a new one? We use PTC's Windchill Bulk Migrator when it suits the project.

Attributes mapped on load

Attributes are mapped as the data is loaded, so files arrive classified and searchable.

Where migrations go wrong, and how we work

Where migrations go wrong

  • Files arrive with the same filenames as data already in Windchill, so they collide on load.
  • The same part was edited on different machines, and the copies no longer match.
  • Part numbers and CAD document numbers need to line up, and the source data does not.
  • Bad data is loaded as it is, and the clean-up happens in production.

Two ways to work with us

  • Full service: we run the migration from up-front scoping through go-live support.
  • Your team, our tools: your people drive the migration with LinkLoader and our guidance.
  • Clean-up included: we cleanse and structure source data before it is loaded, with bulk clean-up tools for what is already in Windchill.

How a migration runs

1. Plan and assess

We define the approach from your system architecture, data complexity and business goals, with data owners and IT involved from the start.

2. Confirm the target

We validate the target Windchill data model early, so there are no surprises late in the project.

3. Prepare, map and transform

Source data is cleansed and structured to fit Windchill through clear mapping and transformation rules.

4. Test early and often

We run repeated test migrations and validate the results before anything is loaded into production.

5. Load and go live

The production load, followed by go-live support while your users settle in.

Upgrading as well?

If the move includes a new Windchill release, see how our Windchill upgrades work.

Is a Windchill data migration on your roadmap?

In a short briefing we review your source systems, your data volume and your target Windchill release.