Migrating to a new machine

Hello

My SW data (parts, assemblies, plans,...) are on the D:\ disk of my PC (HDD). SW is installed on the C:\ (SSD) disk.

I have a new machine with only a 1TB SSD, Windows 10 already installed on the C: drive.

I work alone so I don't have a PDM.
The question is, how do I migrate my data to my new machine without losing the links between plans, parts and assemblies?

Thank you in advance!

1 Like

Hello

Normally, when you open your assemblies/parts/drawings, SW will find its links if the folder names have not changed.
SW may ask for the 1st assembly where the parts are.

So a simple copy on your new disk should be enough.

1 Like

Good evening @yann_4

Happy to welcome you to the forum. :grinning:

Hope we can help you solve a few problems,

The best way is to copy the entire directory without adding or removing anything in the new computer.
If you have items (parts, drawings, etc.) for your ASMs that are in multiple directories, the only 100% secure system is to use the "pack and go" function for each ASM and save it in a ZIP file.
Once the ZIP file is on the new computer, you unzip it and you will be as if you were in the old computer.

The other very very reliable solution but which requires an experienced technician is to copy disk bit by bit by choosing only the directories to copy. It all depends on how you have managed your files.

Kind regards

1 Like

I confirm @opiep27 and @Zozo_mp , the pack and go is not necessary if you move a complete folder without renaming the subfolders.
In this case, Solidworks finds the file and Mep without any problem.
On the other hand, if you rename a subfolder or other, it's more complicated.
On the other hand, if you copy the files, make sure that the original folder is renamed before opening to cut the old links in order to ^'be sure that it opens the files of the new destination.
The pack and go is necessary if the files are scattered in several directories scattered all over a disk, in order to gather everything for example.

2 Likes

Thank you @sbadenis but I'm not sure I understand everything.
The folder structure is:
D:\Clients\Client_A\Projet_A → ASM, PRT, and MEP for Projet_A
D:\Clients\Client_A\Composants_Gen → generic ASM, PRT, and MEP on Client_A
D:\HD\Composants_Gen\ → Generic Assemblies and Parts to All Customers
MEPs are always in the same folder as assemblies/parts but an assembly in the Projet_A contains parts in at least 3 different folders

If I copy the same folders to my new machine but on the disk C:\ SW should find the parts of the assemblies?
Thank you in advance!

1 Like

If you move all your files without moving them between them, he should find his little ones!
At worst, if it can't find a folder, it asks you for the way to a part, and once indicated, it looks for the next ones in the same folder.
The simplest copy everything to your C, unplug the D or temporarily rename your folders and then open everything on the C.
If functional you delete everything on the D and that way no risk of error.

2 Likes

Perfect thanks, I'm installing SW on Monday, March 20th. I'll keep the community posted!

2 Likes

Hello

Lots of very interesting answers, but be careful: SW uses absolute paths.
That is to say that the reader's letter is just as important as the rest!

Personally I will proceed as follows:

  • recreate a D partition on the SDD of the new machine (leave 300GB for Windows and the rest for the D partition), with 1TB it's comfort
  • if possible, extract the D disk from the old machine and plug it into the new one (directly "sata" or in usb with case... to be seen)
  • copy ALL the folders of the old D (it will certainly have a new letter...) to the new D (SSD)
  • remove the old D and test...

In this way, the full path is kept, drive letter + folder tree.
No need for pack&go or having to click on "search..." at each new assembly opening...

If you can't extract the disk, there's nothing to prevent you from using an external disk to do the transfer:
old D → external drive → new D

It may take time but it works, I have already done it following a server change.

Good luck.

6 Likes

Hello;

I will add the need to back up your current Solidworks settings (*. SLDREG) to retrieve these paths on your new Solidworks session.
(Tools menu/"Save/Restore Settings..." »).

And remember to release your Solidworks license on your old PC, BEFORE installing your new PC.

Kind regards.

5 Likes

Sbadenis, more or less that.
It does a bit file by file so it will correct if the successive files in the arbo are in the same corrected folder but if it switches from one folder to another from memory it does not keep the information of the corrected folder and asks the question again.

2 Likes

I would have proposed and pushed for the same solution as @a.eriaud .
Advantage of having 2 partitions, one dedicated to the system, one to data, it allows in case of system formatting not to touch the data.

4 Likes

Hello

Personally the solution I would use.
I will partition the SSD of the new PC to have 2 partitions with strictly the same names as the old one (so resizing C to free up space, creating D on the freed space).
I would duplicate the D from the old PC to the new one
I install SW on the C of the new PC with strictly the same path as the old one.
At some point you have to find ALL the settings files of the old one (the list is exportable): search for files and copy to the new PC in the SAME places.
Export of the parameter file from the old PC.
Copy the settings file to the new PC and copy the settings using this file.

And that's it: you find yourself just like before.

NB: the big advantage of having a partition for solidworks data is that even in case of big problems on the system partition (windows bug...) forcing it to be reformatted, it will not affect the SW data of the other partition (unless crypto virus attacks all partitions).
NB2: for partitions there is a tool in windows otherwise a lot of utilities on the net like "minitool partition wizard"

2 Likes

Hello
First of all, thank you all for your answers. I recreated a D partition on the new machine and then copied (an external disk and with robocopy) the files with the same tree.
And everything works perfectly!
Best regards

2 Likes