How Pulse Transforms Cold Migration in TM1

Cold promotion — stopping TM1 and copying files into the data directory — is one of the most common ways to migrate objects between TM1 environments. Pulse significantly improves this process by automatically resolving all dependencies, eliminating the most common cause of failed migrations: missing objects.

The Problem with Traditional Cold Promotion

When manually performing a cold promote, you must identify and copy every file needed — including all dimensions, attribute cubes, picklist cubes, security cubes, and control objects related to the objects you want to migrate. Missing even one file means restarting the target instance again, which can be very disruptive in production environments.

How Pulse Solves This

Pulse's dependency engine automatically identifies and includes all objects required by the items you select. For example, if you select a cube to migrate, Pulse automatically adds:

• All dimensions used by the cube

• All attribute cubes

• Picklist cubes

• Drill cubes

• Security objects

• Control objects

You never have to manually track what else needs to be included.

What's in an Offline Package

Pulse creates a ZIP file containing two folders:

• items/ — The main objects you selected (e.g. the .cub file and .RUX rule file for a cube)

• dependencies/ — All related objects: dimensions, attributes, subsets, views, and any other linked objects

To complete the migration: stop the target TM1 instance, copy the contents to the TM1 data folder, and restart.

Additional Benefits

• Automatic database backup — Pulse backs up the database folder before applying the package

• Proven at scale — Handles migrations of any size across many client environments

• Works alongside live migration — If downtime is a concern, Pulse also supports live migration (hot promote) which applies changes to a running instance without a restart, with full rollback capability if issues arise

Summary

Pulse transforms cold promotion from a manual, error-prone process into a reliable, dependency-aware migration workflow. The result is fewer failed migrations, less downtime, and greater confidence when promoting changes to production.