Mosaic Schema Extension Object Migration

Starting in Strategy (August 2026), you can migrate Mosaic schema extension objects using package migration.

Object migration handles Mosaic schema extensions as a single model. The package includes the extension and referenced dependencies and conflict policies are applied at the model level. This behavior preserves the extension's mappings, hierarchies, and related schema objects during deployment.

Key Principles

• Migrate the complete extension: Attributes, metrics, facts, tables, and other extension components can not be packaged independently, except for deprecated attributes, where applicable.

• Include outward dependencies only: Mosaic schema attribute mapping includes that attribute. Mapping to an attribute in another extension include the complete referenced extension.

• Respect mapping direction: Reverse mappings are not automatically included. Migrating a Mosaic schema attribute does not include mapped extensions.

• Apply policies at the model level: Components and included dependencies inherit the policy selected for their extension.

Add Mosaic Schema Extensions to Migration Packages

1. Open the Workstation page.

2. Create a migration package or right-click a package and choose Edit.

3. Ensure the package Type is Object.

4. In the Tree view, click Add Objects.

5. Select the check box next to your Mosaic schema and click Add.

6. Expand the Actions drop-down list next to the Mosaic schema and extension objects.

7. If you add an extension component, you are prompted to add the related Mosaic extension objects. An Add Objects dialog displays. To confirm the prompt to package the complete extension and its required dependencies, click Continue.

   If you click Cancel, all selected objects that are not extension objects will be added.

   Objects added automatically as part of the extension are managed through the parent extension and do not have separate actions.

8. Choose one of the following actions:

   • Use Existing: Keeps the existing Mosaic schema objects.

   • Replace: Replaces the existing Mosaic schema objects.

   The selected action applies to the entire extension and its included dependencies. Component-level actions are not available.

9. Click Create or Save.

Conflict Policies

The default policy for Mosaic schemas is Use Existing. The same policy must be used for every extension in a package and is applied to the extension's included dependencies.

Policy	Behavior	Consideration
Use Existing	The target keeps its existing version when possible. If an external attribute is missing from the target extension, Object Migration imports the attribute without its relationships.	Minimizes changes to the target, but relationship definitions may remain different between environments.
Replace	The source model replaces the target model-level definition. If an external attribute exists in the target is not included in the package, Object Migration clears its relationships.	Improves alignment with the source, but removing target relationships may affect report or dashboard results.

All extensions in on package must use the same conflict policy. In Strategy (August 2026), the object migration backend rejects package creation when policies differ.

Migration Scenarios and Constraints

Scenario or action	Status	Behavior and constraints
Schema extension > schema extension	Supported	The target extension is merged or updated according to the selected model-level policy. All extensions in the package must use the same policy.
Mosaic model > schema extension	Supported	If the source and target objects have the same ID, the source schema extension replaces the target Mosaic model. Existing dashboards do not need to be migrated again; extension mappings resolve attributes when dashboards are opened.
Schema extension > Mosaic model	Not supported	The server rejects attempts to revert a schema extension to a Mosaic model. Undo package generation is also not supported.
Schema extension > linked or base model	Not supported	A Mosaic extension cannot overwrite a linked model or base model. Object Migration returns an error to protect model dependencies.
List View	Not supported	Use the standard package-creation workflow in Tree View. You can not use List View to package or manage schema extensions.
Reverse package generation	Not supported	Undo or reverse package generation is not supported.