Using Pulse with Your Existing Migration Process

Pulse supports both traditional TM1 migration methods — hot promote and cold promote — while significantly enhancing them with automated change tracking, dependency resolution, and enterprise-grade governance.

Background

TM1 environments have historically used two approaches for migrating changes between environments:

• Hot promote — Manually recreating or copying objects while TM1 is running (e.g. using Architect or Perspectives).

• Cold promote — Stopping the TM1 service and copying TM1 files directly into the data directory.

How Pulse Enhances Your Migration Process

Pulse supports both methods and adds the following improvements:

Automated Change Tracking

Pulse automatically records every change made in your development environment. This eliminates guesswork and ensures no changes are missed when preparing a migration package.

Dependency Resolution

Pulse's dependency engine automatically identifies and includes all objects required by the items in your package — such as picklist cubes, drill cubes, security objects, and more. You no longer need to manually track what else needs to be included.

Live Update (Hot Promote)

Pulse applies changes directly to a running TM1 instance via the REST API, with no restart required. This is the recommended approach for minimising downtime.

Offline Update (Cold Promote)

Pulse packages the native TM1 files into a structured archive that can be unzipped and copied to the target data directory during a planned maintenance window. This approach integrates seamlessly with existing cold promote processes while ensuring completeness and accuracy.

Both package types can be created from the same migration workflow in Pulse, and both can be applied to multiple target servers.