Migration Best Practices

The Pulse Migration feature is extremely powerful—but with great power comes great responsibility. In this article, we share the key best practices to ensure your migrations run smoothly and efficiently.

If you’re using two Pulse Application Servers, create the migration package on the source server, download it, import it into the target environment, and then execute it.
To avoid compatibility issues, both Pulse servers must run the same version.

Pulse migrates the state of TM1 objects as they exist inside Pulse VCS folder at the moment you create the package.
If Pulse is disconnected or hasn’t captured recent changes, you risk migrating outdated code.
Best practices:

• Configure the Documentation Error Notification Group to receive alerts if documentation fails.

• Review logs and fix issues before creating a new migration package.

• Set up the Invalid Credential Alert for each TM1 instance to ensure Pulse can connect and update objects.

Pulse can migrate cube data live, but this is not the fastest method for large datasets.
For IBM Planning Analytics (TM1), the fastest way to load data is via a TM1 process.
Recommendation:
For large cubes, exclude cube data from the migration package and instead include a process that Pulse executes at the end of the migration to load data efficiently: Executing a Process during migrationPreview

Similar to cube data, migrating large dimensions (more than 5,000 elements) element-by-element is not the fastest way to migrate elements.
Best practice:
Use a TM1 process to load dimension elements and configure Pulse to execute this process during migration.

✅ Following these best practices will help you reduce risk, improve performance, and ensure reliable migrations with Pulse.