🚀 Migrate faster with confidence with Pulse

The Pulse migration features give teams the confidence to move IBM Planning Analytics (TM1) objects between environments quickly — with a clear view of every impact, automatic dependency handling, fast rollback, and a complete audit trail.

Understand all possible impacts

Pulse automatically documents every TM1 object. Its smart documentation gives you the confidence to apply new changes, and makes it easy to compare two instances side by side before promoting anything.

Find changes by developers

TM1 changes can be grouped by developer. Pulse picks up every modification a given developer (or set of developers) has made between two dates, so a migration package can be assembled from real work rather than reconstructed from memory.

Automated dependency detection

When you build a migration package, Pulse finds all related objects automatically. Pick a cube, for example, and Pulse will pull in its rules, dimensions, attributes, and picklist cubes — so nothing required to make the change work in the target environment gets left behind.

Assess impact of model changes

Before executing a migration, Pulse shows you exactly which changes will be applied to the target instance. You can review and selectively include or exclude items — avoiding the "just one line of code" fallacy where small edits cause large surprises.

Maximises application up-time

Pulse migrates TM1 objects live. There is no need to stop the TM1 instance — Pulse applies changes and creates new objects on the fly, so users stay productive while releases ship.

Rollback changes quickly

If a change was migrated by mistake, the rollback feature retrieves a previous version of the affected TM1 process or rule file — without manual file restoration or a full backup recovery.

Optimise processes and workflows

Pulse has fully configurable, role-based security. For example, developers can be permitted to create migration packages while only administrators are allowed to execute them — enforcing separation of duties without slowing teams down.

Improving development quality

Pulse ships with built-in best-practice rules that catch common pitfalls — patterns that tend to slow the system or make support harder later. Naming conventions are validated too, so the model stays consistent and easier to maintain as it grows.

Please your auditors

Pulse keeps a full history of every migration that has happened. Auditors get a clean record of what changed, when, and by whom — and your team gets the option to roll back any of it at any time.

Make TM1 applications faster and lighter

Migrating a large cube, a large dimension, or even a rule change can shift the server's memory profile significantly. Pulse provides reports that help you understand the cause of memory spikes so they can be addressed before they affect users.

In this section

Change Tracking
Pulse's automatic source control logs every TM1 change by author and exact time — across rules, processes, cube structure, dimensions, and dimension data — so you know precisely what to promote. Includes built-in diff tools, point-in-time snapshot exports, configurable change-check frequency, and how the SYSTEM user is applied to offline changes.

Migration
Enterprise-grade migration that overcomes TM1's file-based limitations — covering the four-step Create/Download/Import/Execute concept, the four package methods (All, Documentation Only, Manual, Source Control), automatic recursive dependency resolution, change preview before execution, automatic backups, and the difference between Live (Hot Promote) and Offline (Cold Promote) migrations.