General Info

How Metadata Is Migrated

Understand how file metadata is handled during migration and how to preserve original author and timestamp information.

Overview

During file and site migrations, metadata transfers automatically by default. However, without proper configuration, the original file author, editor, and timestamps may be replaced with migration account values. Understanding how to preserve this metadata is crucial for maintaining accurate file history.

Metadata Fields

👤
Author
Original creator
✏️
Editor
Last modifier
📅
Created
Creation date
🕐
Modified
Last modified

Default Behavior

Without a properly configured mapping table, metadata is handled with standardized values:

What Happens Without Mapping

Author & Editor: Set to the migration account defined in the target connector
Created & Modified: Set to the date and time of migration

Without Mapping Table

Author: migration@company.com
Editor: migration@company.com
Created: 2025-01-15
Modified: 2025-01-15

With Mapping Table

Author: john@company.com
Editor: jane@company.com
Created: 2023-06-12
Modified: 2024-11-03

Preserving Original Metadata

To retain pre-migration metadata values, you must implement a mapping table that correlates source and target user accounts.

What the Mapping Table Preserves

Author

Original file creator's email

Editor

Email of last modifier

Created

Original creation timestamp

Modified

Original last-modified timestamp

Mapping Table Requirements

Critical Limitation

If an entry is missing from the mapping table, the individual metadata will not be migrated. Therefore, the mapping table must be complete from the beginning of the migration.

Mapping Table Structure

Source Email Target Email
john@source.com john@target.com
jane@source.com jane@target.com
bob@source.com bob@target.com

Include All Users

The mapping table should include all users whose metadata you want to maintain, even if you're not assigning licenses to them. Any user who has created or modified files must be in the mapping table.

Best Practices

Complete Mapping Table First

Prepare and validate your mapping table before initiating any migration, including trial phases. Metadata preservation works only when users are properly mapped.

Include External Users

If external users have created or modified files, include them in the mapping table as well to preserve their metadata attribution.

Validate Before Migration

Run a test migration with a small batch of files to verify metadata is being preserved correctly before migrating your full dataset.

Document Exceptions

Keep a record of any users not included in the mapping table. Their files will have metadata set to migration account values.

Was this article helpful?

We value your feedback

Help us improve your experience

What would you like to share with us?

Need direct support? Open a ticket