How Do I Copy Project Data Between Two Azure Blob Accounts?

You copy project data between two Azure Blob Storage accounts with a CDE integration that moves files, folder structure and metadata from one storage account to another, whether in a different region, subscription or organisation. CDE Sync™ connects to both accounts, keeps the project structure intact and logs every transfer.

Why project data moves between Azure Blob accounts

Azure Blob Storage is not a project CDE. It is a destination. Many organisations use it to hold an independent copy of their project data for backup, cold storage, long-term archive or AI search. Once that data is in Azure, there are good reasons to move it again. A contractor may hand a project archive to the owner at completion. An organisation may need to move data into a different region to meet residency rules. Or a merger may mean consolidating storage accounts.

Generic copy tools can move blobs, but they do not understand project structure. Metadata that explains what a file is can be lost, folder logic can be flattened, and there is no project-level record of what moved. For archives that may be needed in a dispute years later, that is not good enough.

What carries across between Azure Blob accounts

CDE Sync™ moves files with their folder structure and the metadata captured when they left the original CDE, such as document number, revision, status and source platform. Version history is preserved where it was captured. You choose which containers and folders move. Every transfer is logged, giving both parties evidence that the archive arrived complete.

The Azure Blob integration page describes the connector in more detail.

How to copy data between Azure Blob accounts, step by step

  • Agree which containers and folders should move, and whether the copy is one-off or ongoing.

  • Confirm the target region and storage tier for the receiving account.

  • Arrange access to each storage account with the relevant Azure administrators.

  • Connect both accounts in the CDE Sync™ wizard and map containers on each side.

  • Run a test on one project folder and compare both accounts.

  • Run the full transfer and keep the transfer log with the archive.

Handover, residency and consolidation

Handover is a common reason. During delivery, a contractor may keep a copy of the project record in its own Azure using CDE Backup™. At completion, the owner wants that record in the owner's own storage account. Copying the archive across, with the structure and metadata intact and a log of every file, gives the owner a record it can rely on for operations and any later claims.

Residency is another. Rules about where project data can sit change over time, and some clients require data to move into a particular region. Moving between storage accounts in different regions, with a full record of what moved, helps you demonstrate compliance. Our article on CDE data residency requirements explains the obligations that often apply.

Consolidation is the third case. After a merger or a restructure, project archives may be spread across several storage accounts. Bringing them together under one account and one structure makes them easier to govern and search.

Storage tier is worth deciding before the copy. Archives that are rarely opened can sit in a cooler, cheaper tier, while records that teams search regularly may suit a hotter tier. Choosing the right tier at the target avoids paying to move the data a second time.

Security and data residency

CDE Sync™ moves data between your storage accounts without holding it, encrypts data in transit and processes it in the Azure region you choose. Data at rest stays encrypted in your own accounts, under your access controls. Utopia Digital holds SOC 2 Type II and Cyber Essentials. See the Security Trust Portal and the global data region map.

Azure Blob to Azure Blob and the Utopiaverse™

An Azure Blob to Azure Blob copy is part of the Utopiaverse™, the connected record Utopia Digital builds across your platforms. CDE Backup™ fills your storage with an independent copy, CDE Migrate™ and CDE Archive™ capture final states into Azure, and AI Insights searches that data with Azure AI search and OCR, giving answers that cite the source files. See also How Do I Run AI Across Multiple CDEs Securely in My Own Azure? and How Do I Connect SharePoint to Azure Blob Storage?

See Azure Blob Storage connected in the monthly live demo, or talk to the team about your project.

Previous
Previous

The value of local data sovereignty. Migrating data between CDEs and regions.

Next
Next

How Do I Connect Asite With ProjectWise or SharePoint?