Performing post-migration steps
The post-migration steps on this page are applicable for migration from 5.x.x to 6.3.0.
Before performing the post-migration steps, ensure you have completed migrating your data.
- If you migrated data between the different deployment modes, ensure you completed migrating data from untethered to tethered.
- If you migrated data between the same deployment modes, ensure you completed migrating data from untethered to untethered and tethered to tethered.
Once all entities are migrated and verified, complete the following steps.
Step 1: Final cluster reload
Run a final full reload of the CAM 6.x.x cluster:
kubectl create job --from=cronjob/loader-job-full manual-full-apimload-job
Step 2: Verify traffic
Test a sample of API endpoints and package keys to confirm traffic flows correctly through CAM 6.x.x before decommissioning your APIM 5.x.x environment.
Step 3: Complete manual configuration in Cloud API Management (SaaS)
The Notification Template Set is not migrated by the migration tool. Recreate it manually on the Cloud API Management (SaaS) dashboard after migration is complete. Refer to Managing Notification Emails for more information.
Step 4: Undeploy the migration pod
When migration is complete, run the following command to remove the migration pod:
cd migrate_5x_to_6/scripts
./undeploy.sh # Kubernetes (default)
./undeploy.sh --env k8s # Kubernetes (explicit)
./undeploy.sh --env swarm # Docker Swarm
