Optional: Encrypt the Migration Data

Note: The Migration Tool cannot import encrypted migration files to the destination database. Encrypted migration files can only be imported using the Import Migration File maintenance form.

The migration file can be encrypted when it is created. You can use this option to avoid storing or transmitting plain text versions of the migration data, which may contain sensitive or personal information. Before exporting a migration file, a public/private PGP key pair must be generated on the WFM application server that is connected to the destination database. The public PGP key is selected when creating the migration file to encrypt the data.

See "File Encryption Using the PGP Library" in the Infor Workforce Management Installation and Configuration Guide for details on generating PGP keys.

Both the Specify and Export and Compare and Migrate options can encrypt a migration file. The Import Migration File maintenance form in the WFM application is used to import encrypted migration files. To perform the import, the administrator logs into the WFM application server that is connected to the destination database. The private key that corresponds with the public key that was used to encrypt the migration file is required to decrypt the migration file. This private key must be present in the destination database.

See Importing data through the WFM application.

Note: The Compare and Migrate option can be used to perform an encrypted export from the source database, but it cannot be used to perform a migration with encryption between the source and destination databases.