Creating a Migration Package with Manual Selection

The manual selection method lets you migrate any TM1 objects between instances by choosing exactly what to include. This gives you full flexibility over the package contents.

Recommendation: Use the Source Control method whenever possible, as manual selection relies on you knowing all changed objects and can result in inadvertently missing items.

Steps to Create a Package with Manual Selection

1. Go to Migration → Create Package.

2. Select Manual as the package source.

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

4. Select the objects to include:

   • Toggle between object types using the radio buttons.

   • Check the Included column checkbox to select individual items.

   • Use Filter, Add Filtered, and Remove Filtered buttons to select objects in bulk.

   • To deselect, uncheck the item in the left panel or click X in the Selected Objects panel.

5. Review the list of files that will be included in the package (1 or 2 files per object depending on type).

Handling Dependencies

After clicking Next, Pulse displays all dependencies found for each selected object. Dependencies are resolved recursively. For each dependency you can choose to:

• Add or update on the target server

• Add if missing (default) — only add if the object doesn't exist on the target

• Ignore — not recommended, as missing dependencies may cause the package to fail

It is recommended to include all dependencies.

Package Types

Provide a name and description, then choose one of the following package 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. Compatible with existing migration processes.