Move an Autodesk Forma or BIM 360 project to another hub, with its issues, RFIs and links intact.

What goes wrong when you move an Autodesk Forma or BIM 360 project between hubs?

• Autodesk's support article on copying a project with all its contents says it cannot be done, and points to the Autodesk Replication Tool for files and folders.
• Autodesk's own blog lists metadata such as issues, RFIs and permissions as things the Replication Tool does not copy. Models it moves have to be relinked by hand.
• The Replication Tool is a technology preview. You request access and add the app to your account before you can use it.
• Autodesk Bridge shares sheets and files with other projects and accounts, but it cannot share files between projects in different regions, and markups are left behind when it shares files.
• Moving a project by downloading and re-uploading files loses the version history and the links between RFIs, issues, sheets and the files they reference, and leaves no record of what moved and what did not.
• Listing a hub's projects needs an Autodesk account admin. A move stalls when the person with admin rights on the source or target hub is not involved from the start.

What are your options for moving an Autodesk Forma or BIM 360 project to another hub?

It depends on how much of the project has to arrive in the new hub. If files and models are enough, Autodesk's own tools may do the job. If the new hub needs the issues, RFIs, submittals and the links between them, you need a tool that moves the records as well as the files.

Common reasons to move are a change of region, consolidating hubs after a merger or restructure, and handing a project to another company's hub at the end of a contract.

What comes across in a SIINC hub migration?

Twenty-four modules, checked against the live Autodesk APIs and grouped below. Every file version comes across, and relationships between records are rewired to the new IDs in the target hub, so linked records still point at each other after the move.

• Hub and project admin. Companies, account roles, project creation and settings, members with roles, and locations.
• Docs. Folders and files with every version, reviews and transmittals.
• Design and model coordination. Revit Cloud Worksharing models and Design Collaboration package copies.
• Build. Issues, RFIs, sheets, submittals configuration, photos, form templates, schedule, assets, meetings, correspondence and specifications.
• Cost and takeoff. Cost management and takeoff configuration.
• Across modules. Relationships, rewired to the new IDs.

How the SIINC Migration Tool moves a project between hubs

Reads and checks before it writes

The wizard reads the source project and checks the move first. Nothing is written to the target hub until you confirm.

One credential, reused across jobs

Each migration runs as one registered Autodesk Platform Services app plus your own consent. The credential is stored once and reused for later jobs.

Any hub the credential administers

Pick a source project in a hub you administer, then any target hub the credential administers, in the same region or another. The new project name is prefilled and editable.

A live ledger of what moved

Every item type shows what was downloaded and created, with failed and skipped items called out. Pacing against Autodesk rate limits is shown, not hidden.

A backup as well as a move

Separately from migration, SIINC backs up 11 Autodesk modules, including files with every version, issues, RFIs, submittals, transmittals and reviews, into Amazon S3 or Azure Blob Storage you own.