What is data migration?
Data migration is the process of updating Autodesk files and design data from a prior release to a newer release.
Do I need to migrate?
It depends. When you upgrade to a new release, migration of files is not essential; files will be migrated on their own when you open and save a file created in an earlier release (R11 - present) to your current release. Legacy data that is out of production does not require any kind of migration process.
Here are some considerations that may lead you to migrate data in advance.
Refer to the table below for more information.
Your data | Recommended Migration method | Why? |
---|---|---|
Few file dependencies Note: A file dependency is any file type that has references to other files, such as derived parts
|
Migration not necessary.
Note: Migration occurs when you open and save a file.
|
Quick and fast If you have no or limited file dependencies - Inventor will do this for you when you open and save a file |
Medium number of files/data sets (100 parts/assemblies or less) | Migrate Command |
Quick and fast The migrate command will find and migrate loaded dependencies. |
Large number of files/data sets (100 parts/assemblies or more) Multiple file dependencies Complex assembly hierarchy Data in multiple folders |
Task Scheduler |
To save on performance Manages the associations for you Note: Task Scheduler manages file associations. This is in contrast to the Open and Save method which migrates a single file on open and save.
|
Custom templates |
On demand migration: No action other than open and save.
Note: If you are not using the Style Library, styles are cached in the template -see FAQ
|
This is the recommended method for migrating custom templates. |
Color Styles, Materials and Appearances | Material Styles Migration dialog box | |
Custom Styles (such as Lighting styles and Drafting styles) | Style Library Manager | This is the recommended method for migrating custom styles, (such as Lighting styles and Drafting styles). |
Custom Content Center libraries | Content Center update process | This is the only available method for migrating custom libraries. |
Skipping releases | Task Scheduler | This is the recommended method If you skip over 1 or more releases. |
Managed by a Data Management System (Vault for example) | Varies - Data Management and Migration | User must consider data volume and document status before proceeding with bulk or piecemeal file migration. |
Do I need to migrate if I am using Vault?
This topic covers considerations related to large data volumes and complications involved in migrating 'released' or locked CAD data.
This topic covers helpful information related to migrating Inventor content.
This topic covers questions asked by Inventor customers
What changed from release to release
This topic covers changes in Inventor that affect migration