Creating a Migration Package

Pulse provides multiple methods for creating migration packages, each suited to different scenarios. All methods produce a package that can be applied to multiple target servers, and all include selected files, dependencies, and any documentation added to each TM1 object.

Note: Pulse does not migrate cube data (with the exception of attribute values). To migrate data, export it using Bedrock.Cube.Data.Export and import it on the target using Bedrock.Cube.Data.ImportFromFile after the migration is complete.

Terminology

• Source — The TM1 instance you are moving changes from.

• Target — The TM1 instance you are applying the migration package to.

Package Creation Methods

Source Control

Pulse records every change made to TM1 objects, allowing you to query changes by date range and by developer. The Source Control method lets you select items to migrate based on this change history.

This is the recommended method once Pulse is actively monitoring your environment.

Manual

Allows you to manually select any TM1 objects to include in the package, regardless of whether they have been recently changed. Useful for migrating specific objects or when source control history is not available.

Documentation Only

Copies the documentation entered in Pulse for each TM1 object from one instance to another. The TM1 objects themselves are not included — documentation is only applied to objects that already exist on the target instance. This is useful for maintaining consistent documentation across multiple TM1 environments from a single source.

All

Includes every TM1 object from the source instance, along with all documentation. Use this method to:

• Move all objects from one instance to another

• Compare two TM1 instances (e.g. dev vs. prod)

Because the package contains all source objects, running it against a target server gives you a clear view of what differs between the two environments. Pulse always performs a comparison before applying any changes to the target.