Best Practices for Moving Teamwork Projects to a New BIMcloud Instance

Issue Identification:

• If you're moving from BIMcloud Basic or a legacy BIMcloud SaaS to a new BIMcloud instance, this guide outlines best practices for preparing, migrating, and sharing your Archicad Teamwork projects.

Solution:

1. Save Projects Using Their Original Archicad Version

For each active Teamwork project:

1. Save a .PLN file to be used for migration.
2. Save a .PLA file as a self-contained backup.
   • A .PLA file ensures you retain all embedded library content and can return to a fully packaged version if needed.
     Recommended settings for saving .PLA backup files 

2. Prepare Projects Based on Status

 a. Inactive Projects
If you have projects that are no longer active or needed in Teamwork:

1. Store both the .PLN and .PLA backups to your company’s file storage.
   • There’s no need to transfer these projects to the new BIMcloud SaaS unless you plan to resume work on them.

b. Projects in the Target Archicad Version
If the .PLN was saved from the same version you're transferring it to (Archicad 28 to Archicad 28):

1. Open the .PLN file in the target version of Archicad.
2. Proceed to step 3

c. Projects From an Older Archicad Version
If the project was created in an earlier Archicad version than the one you're transferring to, you must first migrate the project before transferring it to the new BIMcloud instance.

1. Open the .PLN file in the target version of Archicad.

2. Follow the migration process to update the project to the current version.

3. Resolve any issues flagged by the Library Manager, such as missing or duplicate libraries.

3. Share to BIMcloud

• Once your project is ready, share the .PLN file to your new BIMcloud instance.
  • How to Share a Teamwork Project