TM1 Migration with Pulse – Overview

TM1's file-based architecture makes migration straightforward in principle — but in practice, manually identifying and copying every required file is error-prone. Pulse provides a structured, dependency-aware migration workflow that eliminates the most common migration mistakes.

The Challenge with Manual TM1 Migration

When migrating a cube, you must also include all its dimensions. When migrating a dimension, you must include its attribute cubes and all related control objects. Miss any single object and you will need to restart the target instance again — potentially disruptive in production environments where maintenance windows are limited.

Advantages of Using Pulse for Migration

• Never forget a TM1 object — Pulse automatically identifies and includes all dependencies for every object you select.

• View changes before applying — Pulse shows you exactly what will change in the target instance, including a line-by-line diff of code changes, before anything is applied.

• Automatic database backup — Pulse backs up the database folder before executing each migration.

• Proven reliability — Used successfully by many clients over many years, with ongoing performance optimisations across versions.

How Pulse Migration Works

Migration in Pulse follows two steps:

1. Create a migration package — Select all TM1 objects to migrate from the source instance. Pulse resolves all dependencies automatically.

2. Execute the migration package — Apply the package to the target instance. Pulse compares the current state of the target with the package and applies only the necessary changes.

Migration Methods

Source Control

Query for changes based on a date range and optionally filter by developer. Select the specific changes to include in the package. This is the recommended approach for day-to-day development migrations.

Manual

Manually select any TM1 objects to migrate. Not restricted to recently changed objects — any object can be included (except views and subsets, which require separate handling).

Package Types

Both types include all selected objects and their dependencies, ensuring a complete and reliable migration every time.