Migrating Libraries to ARCHICAD 20

The new version of ARCHICAD will work perfectly well with any older-version ARCHICAD libraries. However, if you stay with your older libraries, you will not get the full benefit of library improvements and fixes in ARCHICAD 20.

We recommend that when you migrate a project to ARCHICAD 20, you also migrate your older-version Library to the ARCHICAD 20 Library, using the easy and automatic Migrate ARCHICAD Libraries function.

IMPORTANT: When migrating an older-version project, if you want to use the newest library, make sure you use the Migrate ARCHICAD Libraries function. If you add and delete Libraries using Library Manager, you may end up with a large number of missing library parts.

Note: The automatic Migration process described below is available only for projects that use ARCHICAD Libraries 10 and later.

Migrate ARCHICAD Libraries when Opening Older-Version Project

When you open an older-version project in ARCHICAD 20, and if your project includes an ARCHICAD Library (version 10 and later), you are prompted to use the Migrate ARCHICAD Libraries function:

Click Migrate ARCHICAD Libraries. This process will do the following:

•

load the new ARCHICAD library

•

load the ARCHICAD Migration Libraries folder (What is a Migration Library? See below.)

•

automatically replace placed objects from the older libraries (versions 13-19) with their latest compatible version in the ARCHICAD 20 library

•

remove ARCHICAD libraries with lower version numbers

The Migrate ARCHICAD Libraries process may take several minutes. Once it is complete, if your project includes objects from pre-ARCHICAD 13 libraries, you may still have missing library parts. In this case, use Library Manager to load Old ARCHICAD Migration Libraries. (What is a Migration Library? See below.)

If instead you choose Skip Migration, you will load the old Library that was saved with the project. All placed objects will be available from that library, but you will not be able to use any library improvements and fixes from the latest version.

Migrate ARCHICAD Libraries for a Running Project

You can use the Migrate ARCHICAD Libraries process at any time, not only when migrating an older-version project. For example:

•

if you did not use the Migrate ARCHICAD Libraries process when opening an older-version project, but now would like to

•

if you have new issues with missing library parts as the project develops (e.g. new library parts added as a result of Teamwork or Hotlinked Modules)

Use the Migrate ARCHICAD Libraries button in Library Manager.

Note: If the button is not shown in Library Manager, this is because ARCHICAD has determined that there is no need for it: all needed libraries (latest ARCHICAD library plus Migration libraries) have already been loaded; and the project has no missing library parts.

Migrating Libraries in a Teamwork Project

To migrate a Teamwork project, use the Migrate Project process described here: Migrating a Teamwork Project (v. 13-19) to ARCHICAD 20.

During this process, make sure that the Migrate ARCHICAD Libraries checkbox is checked. This will ensure smooth migration of your ARCHICAD Libraries together with the Teamwork project.

Note: Some objects in your migrated Teamwork project may be listed as “Temporarily Missing” in the Library Manager or in the Library Loading Report. As soon as other users do a Send and Receive, this problem will be solved automatically.

BIMcloud/BIM Server Libraries in ARCHICAD 20

Change in Library Management

The management of BIMcloud/BIM Server Libraries and their contents has been simplified as of ARCHICAD 20. The “source” library folder, used for Server Libraries in earlier versions, has been eliminated.

Consequently, users no longer have to modify Server libraries in the “source” library folder and then update it using the Manage BIMcloud/BIM Server Libraries dialog box. Instead, users see and edit the contents of the Server library in the Library Manager dialog box.

Restriction on using BIMcloud/BIM Server Libraries Uploaded with Earlier ARCHICAD Versions

In ARCHICAD 20, you can still use libraries uploaded from earlier versions of ARCHICAD.

However, if a Server library was uploaded with an earlier ARCHICAD version, then as soon as you reserve any Library Part or folder from the earlier-version library, its “source” library folder is eliminated (in line with ARCHICAD 20 technology). Consequently, the library and its contents are henceforth editable only with ARCHICAD 20 projects. In older-version projects, the library becomes read-only. (In older-version projects, it will be shown with a lock icon in the Manage BIMcloud/BIM Server Libraries dialog box.))

If you do Reserve such a library, folder or library part in ARCHICAD 20, you receive a warning before you continue.

If you still want to edit this library with older-version projects (e.g. AC 18 or AC19), it is best to click Cancel here, and use the older-version ARCHICAD to reserve and edit the library and its contents.

What is a Migration Library?

Each new version of the ARCHICAD Library contains many objects that have been updated since the previous version. For the most part, these updated objects are compatible with placed older versions of the same object, and will automatically replace the older versions.

Some objects from older ARCHICAD libraries, however, have no counterpart in the new ARCHICAD 20 library (typically, these are “discontinued” objects deemed obsolete). But if you have such objects placed in your project, you want them available even if after migrating to ARCHICAD 20.

ARCHICAD Migration Libraries serve this purpose: they contain only those objects from an earlier-version ARCHICAD Library that do not have counterparts in the latest-version ARCHICAD Library. A Migration Library is much smaller than full-version ARCHICAD Library.

When Are Migration Libraries Used?

Migration Libraries are loaded automatically with two workflows:

•

Migrate ARCHICAD Libraries: This function, used when opening an older-version project in ARCHICAD 20. Migration Libraries are loaded automatically.

See Migrate ARCHICAD Libraries when Opening Older-Version Project.

•

Consolidate: If you have placed objects from multiple ARCHICAD libraries and have loaded all the libraries, you will be prompted to Consolidate your libraries. As part of the consolidation process, Migration Libraries are loaded automatically.

See Consolidate Multiple ARCHICAD Libraries.

If you do not use these workflows which load the needed Migration Libraries, then some of your placed objects from older-version projects may not have a compatible corresponding object in ARCHICAD 20. In this case:

•

Those incompatible older objects will be “Missing Objects” in ARCHICAD 20 if you have removed your old libraries. In this case, you must replace these missing objects with new ones from the ARCHICAD 20 library, and reset their parameters as needed.

•

Keeping your old libraries alongside your new libraries is not recommended, because a great many of the loaded objects will be duplicates and/or superfluous, and increase library loading time and potential errors.

Notes:

•

If you still have missing library parts, it may be because you are using library parts from ARCHICAD libraries earlier than version 13. If so, you must manually add the Old ARCHICAD Migration Libraries folder to the project, using Library Manager.

•

If your ARCHICAD Libraries are BIM Server Libraries (for example, for a Teamwork project) and you want to consolidate them, ARCHICAD will not be able to locate the migration libraries automatically. In this case, you must upload the migration libraries from your hard drive to the BIMcloud/BIM Server.

Where to Find Migration Libraries

Migration Libraries are installed on your computer as part of ARCHICAD installation. They are divided into two folders:

•

ARCHICAD Migration Libraries (for ARCHICAD library versions 13 and up)

•

Old ARCHICAD Migration Libraries (generally available for ARCHICAD library versions 10-12)

You can also download Migration Libraries from the GRAPHISOFT website.

Note: Available migration libraries may vary, depending on your localized version.

Migrating Libraries and Objects from ARCHICAD 12 and Earlier

Note the additional Library-related changes when migrating projects from ARCHICAD 12 and earlier:

•

Active Libraries - Linked Libraries

The active libraries of older-version projects will be loaded in ARCHICAD 20 as linked libraries. (They will be listed in the Linked Libraries folder of the Library Manager.)

•

Other Objects - Embedded Objects

“Other Objects” items in the older ARCHICAD projects will appear in the “Embedded Objects” folder of ARCHICAD 20.

•

Other Objects in Hotlinked Modules

If you place a hotlinked module from ARCHICAD 12, any objects placed from the source file’s “Other Objects” folder will be missing in ARCHICAD 20. The solution is to embed these objects in your host ARCHICAD 20 project, using Library Manager, or to place those objects in a library on the BIMcloud/BIM Server, and add that library to the project.

•

Missing Libraries - Unavailable Libraries

Any library “missing” in the Library Manager of the older version will be listed as “unavailable” in the Library Manager of ARCHICAD 20. Locate these libraries and add them as linked libraries, using the Library Manager’s “Add” command.

•

Missing Objects

Missing objects in the older-version project are also listed as “missing” in ARCHICAD 20, both in the Library Manager as well as the Library Loading Report. To solve the problem, locate the source files of these missing objects and add them to the project, using Library Manager.

•

Unsupported Objects

These files reference unsupported image formats.

For more information, see Image Files in the Embedded Library at Images from QuickTime Formats.

Obsolete Objects

Objects are “obsolete” in two cases:

•

the object has been discontinued entirely as of the new ARCHICAD version (e.g. a computer or TV object that is no longer current)

•

the object has a counterpart in the new ARCHICAD version, but due to changed parameters or functions (e.g. a window whose sash has been altered), the old object will not be replaced automatically

If you use the Migrate Libraries or Consolidate functions as described above, the Migration Libraries will be loaded automatically, together with the necessary obsolete objects, and you won’t have any missing objects.

Note: You will only be able to access only those obsolete objects from the Migration Libraries that have already been placed in your project.

Replace Obsolete Object with Latest Library Part

If you are using an obsolete object (e.g. window from an earlier version) and wish to replace it manually with the newest corresponding library part, be aware that the new window will not be exactly the same as the older one (otherwise, it would have been replaced automatically): something will work differently.

Therefore, when you do replace the old window with the new one, you should reset the new window’s parameters as needed.

To expedite this, use Parameter Transfer: this way, you will pick up the old window’s parameters and inject them into the new window before placing it. This still won’t produce an exact replica, but everything that can be replicated will be, and this will save you manual work.

Use the Pick up Parameters shortcut (Alt+click) to pick up the parameters of the placed object.

Select the old window in the project.

Open the Window Settings dialog box.

In Window Settings, navigate to the new library folder and the corresponding new window that you want to use.

Move your cursor to the new replacement window- and press Ctrl+Alt (Mac: Cmd+Opt). The cursor will change to a syringe shape.

Now click on the new window object to inject the parameters. All transferable parameters of your old window will be transferred to the newly activated window.

Click OK to close Window Settings and to replace the old window with the new one, using the changed parameters.

These modifications to the new window are in effect only until you close the dialog box and place the window; the new window’s default settings will not change.