Autodesk CDE Migration: Moving To and Within Autodesk Forma (formerly ACC)

23 June

If your project data lives in the Autodesk ecosystem, you are probably facing one of three moves: getting off BIM 360 before it is gone, shifting data between hubs at handover, or moving it into the right region for a client or a regulator. The platform names have just changed, which has added a layer of confusion on top, so we will clear that up first and then get into the moves that actually matter.

First, the naming: ACC is now Autodesk Forma

As of 24 March 2026, Autodesk Construction Cloud (ACC) was rebranded as Autodesk Forma. This is a branding change, not a platform replacement, and it does not move or migrate anyone's data on its own. Your projects, files, permissions and folder structures stay exactly where they are. The main things to know for migration purposes are that Autodesk Docs, the common data environment, is now called Forma Data Management, and an Account is now called a Hub.

So when people search for "BIM 360 to ACC" or "ACC migration," they mean the same destination that is now branded Forma. We use both names below, because both will be in circulation for a while.

BIM 360 to Autodesk Forma (formerly ACC)

This is the migration most teams are dealing with right now. BIM 360 is being phased out, and projects need to move onto the current platform before access and support fall away.

The danger is not moving the files. It is everything attached to them. Version history, markups, issues, transmittals and custom attributes are what make the data a usable record, and they are exactly what the quick routes leave behind. Autodesk's own Replication Tool (ART) does not preserve version history and is invitation-only, so it is not a real answer for a project record you may need to defend years later. A manual download and reupload loses the same things, just more slowly.

A proper BIM 360 to Forma migration carries the history and metadata across, not just the current file.

Hub to hub: moving between Autodesk Forma accounts

The second common move is between hubs. A contractor finishes a project and has to hand the complete record to the owner's hub. Two organisations merge and need to consolidate several hubs into one. A joint venture winds up and the data has to be split out to each party.

Native sharing features like Bridge are built for selectively sharing folders between active projects, not for moving a full project record with its history intact. A hub to hub migration at handover needs the whole record to arrive complete and provable, which is a different job.

Region migration and data residency

This is the one most teams discover the hard way. Autodesk Forma data is hosted in regional data centres, such as the United States, Europe and Australia, and a hub is tied to its region. When a client or a regulator requires project data to be held in-country, or a project moves jurisdictions, the data has to move from one regional hub to another.

Autodesk's native tools are not designed to move data across regions. So an organisation that set up in a US hub and now has an Australian client with data residency obligations cannot simply flip a setting. The data has to be migrated, with its history and metadata, into a hub in the right region. This is a genuine and under-served need, and one of the clearest reasons to bring in a migration that is built to preserve the record rather than just copy files.

What Autodesk's own tools leave behind

To be clear about why this needs a purpose-built migration:

Bridge is for sharing selected folders between active projects, not bulk migration with full history, and it does not solve cross-region moves.
The Replication Tool (ART) does not preserve version history and is invitation-only.
Manual export and reupload loses history, metadata and the relationships between items, and does not scale

In every case the files arrive but the record degrades, and the loss is usually invisible until someone needs the history that is no longer there.

How CDE Migrate handles Autodesk migrations

CDE Migrate moves Autodesk data with the record intact, whether you are coming off BIM 360, moving between Forma hubs at handover, or relocating data into the right region. Every migration is scoped against source and destination, audited before it runs, executed with version history and metadata preserved, then validated against the agreed scope with a completion report and audit trail you can hand to a client or an auditor.

Planning an Autodesk migration, or need data moved into a specific region? Talk to us at info@utopiadigital.io.