Migrate settings to new computer

[hydrojock]

I've just completed transfering my AutoCAD 2007 license file to a new workstation and have the program running on the new machine. How do I 'migrate' all my custom settings (toolbars, etc.) to this new computer as well?

 

Thanks!

James

[Jamalama]

I'm not aware of a way to keep your toolbar setup, but you can migrate your cui and pgp files to keep all your shortcuts and settings.

[tottiekop]

Hi

 

I'am having a bit of trouble migrating my settings....... I clicked on the Migrate Custom Settings (AdMigrator.exe) and then it blurts " Migrate Profiles requires that Autocad 2000 or later version be installed on your system" even though I have Autocad 2007 installed....

 

Tried repair install and also registry repair of cad but still the same error message!

 

Is there another way how I can save my current settings?

[GhostRider]

you could try to copy your old profile to the new system as long as the support path are the same

[ReMark]

Put the old hard drive in the new machine and move all the "custom" files you've created over. Then reformat the old HD and use it as a backup.

[VicoWang]

I know this is an older topic, but the pain is still incredibly real. It is absolutely crazy that in 2026, migrating CAD environments still feels like we are stuck in 1999.

 

I actually got so fed up with manually exporting .arg profiles and copying over Support folders that I built a cloud package manager to end this exact nightmare. It's called VedaCAD.

 

The workflow is exactly what you’d expect from a modern development tool. Once you configure your assets on your old PC—whether they are executables (.fas, .vlx, .dll) or environment standards (.ctb, .cuix, .dwt, .shx)—you simply hit Push. Your entire environment matrix is vaulted to the cloud.

 

When you sit down at your new PC, you just log into your account, hit Pull, and within seconds, your exact drafting environment and aliases are flawlessly restored. It is arguably the most elegant solution available right now for CAD migrations.

 

If you are managing an office rollout:

We also built an Enterprise MDM layer for this. As an admin, you can create user groups (Squads) and assign specific toolsets to them from your company's central asset pool. When an employee logs in, their terminal instantly syncs the exact plugins and configs they are authorized for. Group A never even sees Group B's proprietary scripts.

 

No more USB sticks, no more broken network drives. If anyone is currently battling an office rollout and wants to know how to set up this kind of pipeline, just look up VedaCAD or drop me a DM. Always happy to geek out over CAD architecture!

 

Cheers,
Vico