BMC Remedy Migrator executes migrations in two different modes: Migration mode and Scripting mode. BMC Remedy Migrator defaults to the last mode used.
You can also use either Migration or Scripting mode to perform a copy/prefix migration on the same server (see Copy-Prefix migrations).
Depending on how many threads you allocate in the Migration option, you can perform as many migrations simultaneously as there are threads. If BMC Remedy Migrator uses up its allocation of threads, migrations are queued until a thread becomes available. For more information about threads, see Using multiple-threads for multiple migration.
In Migration mode, migrations run immediately.
In Scripting mode, you can create migration scripts that can be saved and run manually at your convenience, or scheduled to run at a specific date and time.
You can use Scripting mode to migrate objects from one server to multiple servers. You can create reusable sets of multiple server migrations and put them in a holding position. This keeps you from having to run each migration separately, one after the other. You can schedule them to run on a specific day and time, or you can open and run them whenever they are needed.
For additional information about migration scripts and scheduling migration scripts, see Creating and saving migration scripts and Scheduling scripted migrations.
When using only one server, you cannot migrate identically named objects to the same server. You must change the prefix before a migration can begin. In a Copy/Prefix migration, you migrate objects to the same server, and then change the object's prefix in the Prefix dialog box. See, Migrating objects to the same server.
The Copy/Prefix migration runs in either migration or scripting mode. It is useful for doing simple development or testing of workflow on the same server. It also keeps all the relationships between forms and related workflow separate.