Return of Library Migration

AUPa
Contributor

It would be extremely helpful if the Archicad library could be migrated as before. Otherwise, it would be beneficial to create an immediate tool (goodie) that would allow us to do so. It is essential that this capability is available in the future.

 

Graphisoft, you need to understand that a project lasts at least one year; in our office, our projects range from 2 to 5 years. This new limitation significantly reduces the value of the annual Archicad updates. Library updates were one of the main reasons for updating Archicad, and I believe this is true for many users. In our case, what should we do? Wait several years before updating Archicad and cancel our monthly subscription?

 

Please reintegrate library migration.

4 Comments
Barry Kelly
Moderator

Migration will continue from 28+, you just won't have to 'migrate' anymore as it will be automatically controlled (as I understand it).

 

If you are working on an older file (27 or before), you can still open it in 28 and continue using the 27 library.

In that case I would not load the 28 library packs as well, just keep working on your 27 file as it is but using the 28 program.

 

Barry.

AUPa
Contributor

The library migration in Archicad no longer works as it used to, where it happened automatically. In versions prior to Archicad 28, when opening a project file from an older version, for instance, from Archicad 26 to Archicad 27, the library would automatically migrate to become the library of the new version. However, with Archicad 28, a file originating from Archicad 27 retains the library of its original version.

 

This means that new objects in the Archicad 28 library are not available, such as the pictograms, new vehicles, or Japanese objects. I reached out to support, who confirmed that Archicad 28 no longer allows library migration from previous versions. As a result, a project started in Archicad 27 must be completed in that same version, which is why I’m sharing this information.

 

In short, I’m using a file that was originally an Archicad 27 file in Archicad 28, but I am not able to take advantage of the Archicad 28 library—I don’t have access to its objects. Ideally, it should be possible to use the new library on an Archicad 27 file that has been converted to Archicad 28.

Barry Kelly
Moderator

There was a deliberate decision by Graphisoft not to migrate the 27 object to 28, and this has been clearly documented from the start of beta testing.

Nothing is going to change now.

 

You have 2 choices.

Open the 27 file in 28 and keep using the 27 library - oddly this library is found in a folder called 'Archicad Library 28', but it is the 27 library.

So just load that folder as you would have done in the past.

 

BarryKelly_0-1730798361082.png

 

No, you will not have any 28 objects if you do this.

Also load the Migration Libraries if your job has used older libraries in the past.

This is exactly the same as before, except that you are using the 28 program.

 

 

You can also choose to load the 28 Library Packages as well.

You can load all of them or just the ones you want, like the Japanese objects.

 

The problem if you load the 27 library and the library packs, is you will end up with a lot of duplicates.

Not so much the objects because they are not duplicates (which is why they don't migrate), but a lot of images for the user interface and surface materials.

You just have to ignore them.

 

BarryKelly_1-1730799000103.png

 

And now when you search for an object to place, you may have 2 of everything.

One will be from the 27 library (and will have "27" at the end of its name, and the other will be from the 28 library.

 

BarryKelly_2-1730799220944.png

 

 

This could be confusing and why it is not recommended that you do this.

It is recommended that you only load either library.

Load 27 if you want to continue working on an old file and load 28 when you are starting a new file from a new 28 template.

 

Barry.

 

 

 

 

AUPa
Contributor

This is precisely what I reproach Graphisoft for. That’s why I created a wishlist.

 

As you mentioned, it is not recommended to handle this migration manually. So why not allow one last automatic migration of the library or create a special tool (goodie) to do it?

Status
Open

with 0/200 Votes 0%

Wish details