Note
Links to additional Frequently Asked Questions (FAQs) can be found at the end of this guide.
This article answers common questions about how metadata is handled during migration. It also helps you troubleshoot issues, so you can identify why metadata did not migrate as expected and how to resolve it.
Metadata Migration FAQs
This section provides answers to frequently asked questions about metadata migration.
Do I need to turn anything on?
No. Metadata is ticked by default in the item selection menu before submitting the migration pass.
Is the whole term store migrated?
No. Only the term sets used by the migrated managed metadata columns, with all their terms. The System, Search Dictionaries and People groups are never migrated.
What if the destination already has the same term set?
If the ID and name both match it is reused and left unchanged. If only one matches, it is a conflict and is skipped with a warning.
I renamed a term at the source. Why did it not change at the destination?
Renames and deletions are not carried over. They show as conflicts and the destination stays as it is.
Are multi value managed metadata columns migrated?
No.
A file was empty in a column at the source. Why does it have the default value at the destination?
On the first pass it stays empty. On later passes the column already has its default, so a new file that is empty in that column gets the default, just as an upload by hand would.
Are choice colors migrated?
Yes, for columns the migration creates
Does the user mapping apply to Person columns?
Yes. The UserMapping advanced option is used for Person columns, Created By and Modified By.
Are lookup and rating columns migrated?
Only in SharePoint Sites (site to site) projects. In SharePoint Online and OneDrive migrations they are left out by design.
Will files I migrated before get their tags and pictures now?
Only if they are migrated again after the source file has been updated. A file is migrated again when its been changed at the source (creating a new version) and another migration pass is ran.
A column has a warning that a setting could not be set. Was the column migrated?
Yes. The column and its values are there. Only the named setting is missing. Set it on the destination column by hand. Migrating again does not change an existing column.
Why do older versions show the right author now?
Each version keeps its own Created By and Modified By instead of arriving as the System Account user.
Where do I see what went wrong with columns or terms?
In the line item migration errors and warnings, under the Columns folder.
Metadata Migration Troubleshooting
This section describes common issues that can occur with metadata during migration. For each issue, it explains the likely cause and the steps to resolve it, so you can restore missing or incorrect metadata in the destination.
| Symptom | Cause | Resolution |
|---|---|---|
| Managed metadata tags missing on some items | The term set or term did not migrate (conflict, or refused by the destination) | Check the warnings on the Columns folder, fix the conflict, then migrate again |
| A managed metadata column is missing at the destination | Its term set is not at the destination, or a different column with that name already exists | Follow the Columns folder messages, then migrate again |
| A term group, term set or term was not migrated because of the same ID or name | The destination has one with the same ID but another name, or the same name but another ID | Rename either one to match, or delete the destination object, then migrate again |
| Values still show View entries | The destination column still has Append Changes to Existing Text on | Migrate again. If the warning below appears, turn it off on the destination column |
| Pictures missing in an image column | The picture is over 25 MB, the library pictures exceed 200 MB, or the destination refused it | Check the image column messages on the Columns folder |
| Older files do not show new column values | They were migrated before and have not changed since | Only files changed after the last pass started are sent again. Run another migration pass. |
| A multi value managed metadata column is missing | Not supported | Working as designed |
| A column's settings differ from the source | The column already existed at the destination | Existing columns are never updated. Fix them at the destination |
| A column has no default value, validation, unique values setting or formatting, with a warning that it was migrated, but its ... could not be set | Setting it at the end of the pass failed. The warning ends with the SharePoint error | Set it on the destination column by hand. For unique values, remove the duplicate values first |
| An information warning says columns have a default value, a unique values setting or validation | Shown once, on the pass that created those columns | Working as expected |
| On a later pass, empty files got the default value or some files were refused | The default, unique values or validation is now in place | Working as designed. For refused files, fix the duplicate or invalid value, then migrate again |
| A Number column shows the wrong separator or unit, with a warning that its display settings could not be set | The second step after creating the column failed | Set the number format on the destination column by hand. Migrating again does not fix it because existing columns are never updated |
| Column type not supported for a multi-line text, Currency, Hyperlink or Location column | The column could not be created. The text appears for any creation failure of these types | Check the account permissions at the destination, then migrate again |
| A Person column shows someone who was removed at the source, or an older person | The value was cleared, or the newer person could not be found, in a later version | Working as designed. Correct the value at the destination |
| Site to site: a file is missing its later versions, and the item error says Lookup list ... was not found in LookupListMap.xml | SharePoint refused the hidden lookup that managed metadata values use | Contact support |
Messages You May See
This section lists the messages you may see during migration and explains what each one means and how to respond.
| Message | Meaning and action |
|---|---|
| Term store changes were made, but the final save failed: {error}. Migrate again | Migrate again |
| Term store was not migrated because of an unexpected error: {error}. Migrate again |
Migrate again. If the term store did not change at the source, contact support |
| Managed metadata column '{name}' was skipped because its term set is not at the destination. Migrate again once the term store has migrated | Migrate again after the term store arrives |
| Managed metadata column '{name}' already exists at the destination but is not a managed metadata column. Rename it at the destination, or delete it, then migrate again | Rename or delete the destination column, then migrate again |
| Term group '{name}' was not migrated. The destination site already has a site-level term group, '{dest}', and a site can have only one... | Rename either group to match, or delete one, then migrate again |
| Could not turn off 'Append Changes to Existing Text' on '{name}'. Its values will show as 'View entries'... | Turn it off on the destination column, then refresh |
| Column '{column}' in library '{library}' was migrated, but its {setting} could not be set: {error}. Set it at the destination by hand | Set the named setting by hand. For unique values, turn it on once duplicates are fixed |
| Image columns could not be migrated: {error}. Items with pictures in them will arrive without those values. Document migration was not affected | Migrate again. Contact support if it repeats |
| Failed to read the pictures for image columns from the source. Image column values will arrive empty | Migrate again. Contact support if it repeats |
| Failed to export the term store. Managed metadata column values may not resolve at the destination | Migrate again. Contact support if it repeats |
Still need help?
Contact support and include:
- the project name and the line item that shows the problem.
- the exact message you see, copied as written.
- the date and time of the run or pass.
- a screenshot of the line item or screen.
Related Topics
- Teams Channel Selection Frequently Asked Questions and Troubleshooting
- Flex Collaboration License Frequently Asked Questions and Troubleshooting
- Version History Frequently Asked Questions and Troubleshooting
- Permission Fidelity and Re-sync Frequently Asked Questions and Troubleshooting
- SharePoint Sites Site Level Content Frequently Asked Questions and Troubleshooting
- SharePoint Sites Sensitivity Labels and Encryption Frequently Asked Questions and Troubleshooting
- SharePoint Sites Migrations Frequently Asked Questions and Troubleshooting