If SAP®PLM is used to manage SOLIDWORKS data, the files stored in the PLM system are not automatically migrated to the new version of the CAD system CAD version with which they were last saved. This leads to an increased memory requirement over time and, above all, to much longer load times of the modules and parts.

Our CAD Migrator migrates the modules and parts stored in SAP PLM at the push of a button for the latest version of SOLIDWORKS. The software solution is managed centrally via SAP® and uses several PCs for the migration simultaneously, at times when the computing power is not otherwise required.

For example, more than 100,000 files can be migrated over a weekend!

Process of migration

A migration is an adjustment of CAD files consisting of several steps and, if necessary, several migration sets, which causes the same change to the CAD files. Starting CAD migrator asks for firstly set the type of operation to either a new migration or a migration step.

You always have full control over the migration process. Existing files are retained even after the migration has been completed. While a new, active content version of the CAD file is created for each migration, the old version is retained as an inactive version. When a new migration is carried out, a new, active content version is created, the result of the first migration is retained as a non-active content version, and the content version is only deleted with the CAD file, which is still in the state before the first migration.

It is also possible to stop the migration process in the CAD migrator. As soon as the command for stopping is executed, no more jobs are delivered to the migrators. When all outstanding migration jobs are executed, the CAD migrator remembers the last processed number to the migration set and stops. Restarting after a stop is easy because the CAD migrator maintains the status at each stop for each migration set. This allows the migration to continue with the next file.

Standard features of the CAD Migrator

Central configuration of the migration in the control program

In the control program, you have the option to configure the migration with the following options:

  • Autostop
  • current day
  • Strategy in the event of conflicting versions
  • workstation applications to migrate
  • configuration of a migration set

The migration can be set in a way to run only on specific days and for specific number ranges. This allows, for example, to use nighttime and weekend times when the SOLIDWORKS workstations are not being used.

The migration record is selected via the screen, which is also used in the standard SAP transaction CV04N. Subsequently, this migration set can be filtered. The following options are available for filtering:

  • Select all versions except the last released.
  • Select all versions except the last one.
  • Delete the document if it is the element of an assembly. (These elements are automatically migrated when migrating the assembly containing them.)
  • In addition, you can also manually delete hits from the migration set.

Configuring Migrator PCs

Migrator is the PC program that runs on a CAD workstation and performs the actual migration. The migrators register as so-called "RFC servers" on the SAP system. During installation, a "program id" is specified, via which the Migrator registers with the control program. In SAP, an RFC destination is set up for each migrator, which is connected to the program id of the associated migrator by configuration.

Assembles dissolved

If the CAD migrator has found a CAD file for conversion, it first checks whether it is an assembly. If it is, the associated document list is dissolved. The originals to be considered are then determined and checked to see whether they have already been migrated. This information is stored together with the module structure in a program-internal migration list. The next step is to wait until a free migrator (on a CAD workstation) is available. When this is the case, further tests are carried out. These determine whether the elements contained in the migration list are currently in a different migration or have been set to an error status during another migration. If neither is the case, the migration list is transferred to the free migrator for processing. If a CAD file is completely converted, this is noted in the database table. From this point on, the migrated file can also be used in other assemblies.


A roll-back to the previous version of the CAD file is possible, as the old version is still available as an inactive version. In the case of a rollback, the CAD migrator offers a corresponding function which replaces the CAD files with the previous content versions for the selected migration set.



Trademark Attribution: SAP and SAP ERP are trademarks or registered trademarks of SAP AG in Germany and in several other countries.