How to Move Files to a New Data Room

Moving a data room is more than copying folders. The new workspace must contain the intended files, expose them to the right groups, and provide usable new links while preserving required historical records.

Plan the cutover before transferring sensitive material. Keep the old room available to authorized administrators until reconciliation and approval are complete, subject to your retention and subscription arrangements.

1. Build a source inventory

Record every item in scope: folder path, file name, version, size and owner. Include hidden or archived material only when the responsible owner approves its migration. Record empty folders separately if their structure matters.

Create a second register for access groups, recipient identities, invitation status and special restrictions. Export available audit records through the provider's supported tools and preserve them separately from the content copy.

Do not assume a ZIP of documents includes permissions, analytics, agreement records or working links.

2. Define the destination and cutover window

Confirm that the new service accepts the required formats and sizes and supports the access model the project needs. Test a harmless folder before transferring the full collection.

Choose a point after which edits to the old room will stop or be tracked as a separate delta. Otherwise, a source file may change after it was copied and before the new room becomes active.

Name the person who approves the cutover and the person who handles recipient support. Set a rollback trigger, such as unresolved missing files or permissions that cannot be reproduced. Migration speed should not replace a clear approval decision.

3. Transfer approved files and reconcile

Use the provider's authorized export and upload workflow. Investigate export warnings before treating the transfer as complete. Digify documents examples such as problematic paths and duplicate names; those examples are provider-specific, not universal limits. Digify: Export errors and potential fixes

Compare the destination manifest with the approved source scope. Check counts, paths, sizes and the correct release versions. Where byte-identical transfer is required, compare file hashes using an approved local tool. Explain transformations rather than marking changed files as identical.

Open representative documents in the new viewer. Include a large file, nested folder and any format with important interactive features. Record missing, changed and deliberately excluded items separately.

4. Rebuild and test permissions

Create destination groups from the approved permission map. Confirm who can view, download, upload or administer each location. A copied folder name does not carry its former restrictions with it.

Use harmless samples and test identities for both allowed and blocked paths. Check direct-file links as well as room navigation. Remove test access after verification.

Do not rewrite old activity records as though they were generated by the new system. Preserve their provider, time range and original identifiers. Incoming recipients should receive new invitations or links according to the destination's actual workflow.

5. Approve the switch and retire the old path

Before notifying recipients, confirm file reconciliation, permission tests and the support contact. Send one clearly identified destination URL with any changed access instructions. Update internal references and record old-to-new link mappings.

Monitor the agreed transition period for missing-file and access reports. If the rollback trigger is reached, follow the recorded plan rather than creating competing active rooms without explanation.

Close old external access only after approval and required record preservation. Retaining an old administrative archive is a separate decision from allowing recipients to keep using obsolete links.

Frequently asked questions

Will permissions transfer automatically?+

Do not assume so. Confirm the supported migration mechanism, rebuild the approved map where necessary and test actual destination identities.

Should I delete the old room immediately?+

Wait for reconciliation, cutover approval and the required retention decision. Disable obsolete external paths separately from preserving authorized records.

How should old audit records be stored?+

Keep available exports with their source provider, date range and identifiers in approved storage. They should remain distinguishable from activity generated in the new room.

Before you share

Complete migration when the approved files reconcile, recipient access is tested, current links are documented and the old room's closure or retention has an owner.

Related articles

• How to Share Multiple Files With One Link

• How to Update a Shared File Collection

• Single File or Deal Room: Which to Use?

• Fix Data Room ZIP Download Errors

Sources and editorial disclosure

Primary documentation reviewed October 11, 2026. Product settings and entitlements can change; use the linked help for current details.

• Digify: Export errors and potential fixes

VDR Directory is published by the SendNow team. SendNow is included where relevant to the task. This guide is based on public documentation and editorial recommendations, not a claim that a signed-in product demonstration was performed. Stock photos illustrate the topic; they do not show the described product interface or prove feature behavior. Examples and verification checklists are illustrative unless explicitly stated otherwise.