Project data & BIM
About BIM-based management of attributes, schedules, templates, favorites, hotlinks, projects in general, quality assurance, etc.

Any tips on migrating to V13?

Arcadia
Booster
Shortly I will have the option of upgrading to v13 from v12. I have not done this before as I bought into the system on v12. I need to buy upgrades from cadimage for their accessory tools (they say the v12 ones won't work on v13) as well as an upgrade for the 3d edge library (which some Aus users may be familiar with). How will the upgrade affect other 3d objects I have - will they still work? What will happen when I open jobs completed in v12 in regards to objects libraries and v12 cadimage accessories? Will favourites have to be updated? Will I lose any custom materials I have created when i install the upgrade? Any help in this regards would be appreciated as I am a little nervous about the process - I have set things up pretty well for my work flow and i don't want to have to spend time re-organizing things or updating previous job files I need to work on. Thanks.
V12-V27, PC: Ryzen 9 3950X, 64g RAM, RTX5000, Win 11
20 REPLIES 20
Karl Ottenstein
Moderator
lec1212 wrote:
So all my favorites settings GONE
in upping to 13?
lec
No, not at all. All of the Favorites will be there ... but will refer to library parts in the 12 or earlier library. So, all Favs for walls, columns, etc will be just fine. It will only be the Favs for library objects - notably windows/doors - that would have to be updated if you want them to refer to the corresponding 13 library parts. Same migration issue as all prior versions.

Cheers,
Karl
One of the forum moderators
AC 27 USA and earlier   •   macOS Ventura 13.6.6, MacBook Pro M2 Max 12CPU/30GPU cores, 32GB
Arcadia
Booster
Trouble is most of my favourites refer to third party 3d objects/windows/doors etc.

What happens to complex profiles and composites that have been set up?
V12-V27, PC: Ryzen 9 3950X, 64g RAM, RTX5000, Win 11
Anonymous
Not applicable
That's a relief.
Guess I didn't read the post close enough.
Thanks
lec
Karl Ottenstein
Moderator
Arcadia wrote:
What happens to complex profiles and composites that have been set up?
Any attributes (such as those) will be present when you open the file. Nothing new - whatever was there will be there.

There really are not many issues involved in migrating. As always, there is no requirement that you use the newer libraries. You can always save a PLA from the old version and open that in 13 - or open the PLN using the old library folders.

Karl
One of the forum moderators
AC 27 USA and earlier   •   macOS Ventura 13.6.6, MacBook Pro M2 Max 12CPU/30GPU cores, 32GB
Arcadia
Booster
And will the package I get from Archicad as a select client be upgrade software or a new package? Ie can I run both v12 and v13 on my system for a time as needed. Maybe I should ask graphisoft this question but I usually get quicker answers from this board than them.
V12-V27, PC: Ryzen 9 3950X, 64g RAM, RTX5000, Win 11
Karl Ottenstein
Moderator
Arcadia wrote:
And will the package I get from Archicad as a select client be upgrade software or a new package? Ie can I run both v12 and v13 on my system for a time as needed. Maybe I should ask graphisoft this question but I usually get quicker answers from this board than them.
Graphisoft does not distinguish between new and upgrades (other than the delivery of a protection device with a new license). The package and disk are the same. Any licensed user may legally run all prior versions of ArchiCAD that their protection key is compatible with.

The key situation is important to be aware of:
http://www.archicadwiki.com/ProtectionKey

Note that with a WIBU key (blue USB keyplug), you can run versions 6 through 13 (current).

Codemeter keys can currently ONLY run 13. As noted in that Wiki article, patches for 10, 11 and 12 are supposed to be released later this month that will allow them to be run with Codemeter. But, it sounds like there is no intention of supporting any earlier versions which will limit Codemeter users to the read/write capabilities (for older projects) listed here:
http://www.archicadwiki.com/ArchiCAD%20versions

Cheers,
Karl
One of the forum moderators
AC 27 USA and earlier   •   macOS Ventura 13.6.6, MacBook Pro M2 Max 12CPU/30GPU cores, 32GB
Arcadia
Booster
That's very useful info. Thanks Karl.
V12-V27, PC: Ryzen 9 3950X, 64g RAM, RTX5000, Win 11
Anonymous
Not applicable
Everyone talks about 'migration' like it's a command or menu selection or something. What are the steps involved in "migrating"? I don't think I fully understand the concept, let alone how to do it?
David Larrew
Booster
"Migrating" refers to being able to update an older version AC file to work successfully within the new version. The AC13 documentation has "migration" instructions that will help you if you choose to upgrade an older file.

Many firms choose not to migrate older files and just finish the older project up in the older version of AC. Only starting new projects with the new version - In this case AC13.
David Larrew, AIA, GDLA, GSRC

Architectural Technology Specialist

a r c h i S O L U T I O N S



WIN7-10/ OSX 10.15.7

AC 5.1-25 USA
Anonymous
Not applicable
Skaman40 wrote:
Now migrating an existing Teamwork project into AC13 is a different story...
only received v13 couple of days ago, so haven't tried this; therefore, based on nothing but speculation:

- sign in to v12 teamwork file with exclusive access and save as .pla archive;
- open .pla archive with v13 and share as teamwork file.

in theory this should work, YMMV (see below )