About the pcemigrate Tool
The pcemigrate tool helps in transitioning on-prem customers to SaaS by facilitating object migration between two PCEs. It is compatible with Linux (recommended), macOS, and Windows, and provides these features:
Exporting and applying managed workload metadata.
Generating and encrypting VEN migration parameters in a YAML file.
Workloads migrated using the database backup are transplanted and don't need
venmigrateinstalled.Any workload paired after the database is restored will require
venmigrateinstalled. They are not transplanted, but they are unpaired and re-paired.Deleting subsets of unmanaged workloads based on filters.
Unpairing managed workloads based on various filters.
Persistently storing migration information to resume operations.
The workflow for on-premise PCE to SaaS migration involves setting up the organization in SaaS, migrating policy objects and optionally management objects, and migrating VENs in sets by creating unmanaged workloads, pairing them, and applying custom labels.
Synchronization of policy objects and workload changes between the two PCEs occurs during VEN migration. After migrating to SaaS, unmanaged workloads are removed from the on-premise PCE, and redundant ones are removed from SaaS.
Using the pcemigrate Tool for Standard Migration
When using the pcemigrate tool for standard migration, review these options.
Preservation of Provisioning State for Policy Objects
The initial migration and synchronization process occurs in two phases:
Snapshot of Provisioned Versions
Migration and sync include all currently provisioned versions of policy objects.
Snapshot of Draft Versions
Migration and sync also include draft versions of policy objects.
Provisioning with the command pcemigrate migrate/sync
The --provision option has been removed from the
pcemigrate migrate/synccommand.As a result,
pcemigrate migrate/syncnow takes longer to complete.The provisioning state is preserved using the
pgdump- based initial migration.
pcemigrate Syntax
pcemigrate command \[flags]where
commandis the specific command to execute. For example, the label-export command exports labels to a JSON file.flagsare optional parameters. Some of the parameters are global and can be specified for all commands.
Examples are: --verbose, --debug, --pce.