New Baseline migration FAQ

This FAQ addresses common questions related to New Baseline migration, behavior changes, migration considerations, and expected outcomes when upgrading to the New Baseline model.

What are the key benefits of migrating to the new baseline?

The New Baseline model provides several improvements, including:

Does baseline migration create new baselines for all versions of a map?

No, the migration process creates new baselines only for the current working copy of the map. Baselines associated with other working copies are not included in the migration.

What happens when a user reverts to a previous version of a map?

When a previous version of a map is restored or accessed, the baselines associated with that version are automatically migrated to the new baseline model by an asynchronous migration process.

Are invalid references migrated to the new baseline?

No, invalid references are skipped during migration to maintain baseline consistency and ensure the reliability of the migrated baseline.

Does baseline migration change the baseline?

Baseline migration retains all valid baseline content and references exactly as they are. Invalid references, however, are not included in the migrated baseline. Apart from the removal of invalid references, migration does not introduce any changes to references or dependency resolution behavior.

Any further changes to references or dependency resolution can occur only after the migrated baseline is modified, rebuilt, or newly created using the new baseline model.

Until one of these actions is performed, the migrated baseline continues to reflect the original baseline definition.

Are reltable references included in the new baseline model?

No, references originating from reltable elements are excluded from baseline resolution, consistent with the behavior of the legacy baseline model.

How are DIRECT references handled in New Baseline?

In the New Baseline model, the direct map references are explicitly classified as DIRECT references. During migration and baseline resolution, these references are given the highest precedence and are resolved before all other reference types.

Are scope="peer" references included in the baseline?

No, references with scope="peer" are not included in the baseline model. Excluding these references improves publishing performance and avoids unnecessary dependency resolution.

Can baselines still be managed from the Map Dashboard?

No, the baseline management is supported only from the Map Console in New Baseline.Creating and managing baselines from the Map Dashboard is not supported.

Is any precaution required during migration?

Yes, baseline modifications should be avoided while a migration is in progress, particularly in working copies. Making changes to baselines during migration can lead to migration failures and may leave baselines in an inconsistent state.

What happens if versions are missing after migration?

Some baselines may need to be rebuilt after migration if the versions referenced by those baselines are no longer available or accessible.

What is the approximate time required to migrate baselines for an On-Premise setup?

Migration time depends on several factors, including:

Based on internal testing and observations from repositories containing approximately 18,000 references, migration duration can vary significantly depending on the repository structure and operating environment.

Can we rollback to Old Baselines again?

Yes. However, when a rollback is performed, the old baselines are restored to the state they are in at the time of migration. Any changes made while the old baseline configuration is disabled and the new baseline configuration is active are not reflected in the restored baselines.

The original old baseline objects remain available at their original location. When the new baseline configuration is disabled, the system automatically switches back to using those original objects.

How can we migrate to New Baselines?

To migrate to new baseline, follow the steps in Migrate to New Baseline.

Can we migrate to the new baseline at any time? Are there any prerequisites?

Yes. You can enable the new baseline at any time, as long as your environment meets the minimum version requirements.

Prerequisites:

Once these requirements are met, you can migrate your existing old baselines to the new baseline model and start using its capabilities.

Is it necessary to back up the current server state before migrating to the new baseline?

No additional backup is required specifically for migration to the new baseline.

However, baselines associated with the working copy can be lost if a user later performs a version revert operation. This behavior is not unique to the new baseline model; reverting to an earlier version can also remove the corresponding old baseline working-copy nodes.

If preserving working-copy baselines is important, it is recommended to back them up before migration. After migrating, users will primarily work with new baselines, but a subsequent version revert can still result in the loss of working-copy baselines.