/
Creating a Migration Package from Source Control

Creating a Migration Package from Source Control

Using source control as the basis for a migration package is the most reliable way to ensure all relevant changes are included. Pulse tracks every change as it occurs, allowing you to identify changes by date range and by user.

Prerequisites

Before creating migration packages, ensure that Change Tracking and Source Control are enabled in Administration β†’ Instance Settings.

Note: Pulse only tracks changes from the point when these features are enabled. For historical changes made before enabling them, use the Manual selection option when creating a package.

Steps to Create a Package from Source Control

  1. Go to Migration β†’ Create Package.

  2. Select Source Control as the package source.

  3. Select the TM1 instance you want to migrate objects from.

  4. Select the date range to identify changes.

  5. Optionally, filter by one or more users to restrict the change list.

  6. Review the list of changes matching your criteria and select the ones to include in the package.

Optional: Check Source Control

Enable Check Source Control to query the source control history for each item and record who last changed the file. This information is stored in the package for auditing purposes. Note: this option is disabled by default as it can be slow when there are many items.

Handling Dependencies

After clicking Next, Pulse displays all dependencies it has found for each selected object. Dependencies are resolved recursively, so there may be many for each object. For each dependency you can choose to:

  • Add or update the dependency on the target server

  • Add if missing (default) β€” only add the dependency if it doesn't already exist on the target

  • Ignore β€” skip the dependency (not recommended, as it may cause the package to fail)

It is recommended to include all dependencies.

Package Types

When saving the package, provide a name and description, then choose one of the following types:

Live Update (Hot Promote)

Executes against a running TM1 instance without requiring a restart. Does not migrate cube data, views, or subsets. Minimises downtime.

Offline Update (Cold Promote)

Packages the native TM1 files for manual copy to the target data directory after TM1 is stopped. Supports migration of cube data, views, subsets, and all other TM1 objects. This is the traditional migration approach and allows Pulse to integrate with existing migration processes.