Multiple tier environments

We can migrate each tier independently, or we can migrate the lowest tier, and use staging to production techniques to build out the other tiers.

Migrate tiers using staging to production techniques

The lowest level tier is migrated, and then that tier is moved to the next levels using staging to production techniques. For example, if we have Development, Authoring, and Production tiers, we can migrate the development environment and use staging to production to move that environment to the new authoring and production tier.

Hasten slowly with this approach. Ensure artifacts, settings, custom apps, and shared libraries are properly moved to the next tiers. Plan for a test phase that validates the application before moving to the next tier.

Ensure managed pages enablement in the higher-level tiers matches. Migration from a version before Version 8 leaves the managed pages feature off. If we build new higher tiers using the Portal installer, then managed pages are turned on.

Migration ensures that all settings in the lowest tier are migrated to the target environment, but since the higher tiers are newly built, they need to be tuned. Tuning might also be necessary on the lowest tier, if the tuning recommendation changed since the previous Portal version. Consult Portal tuning guides.

Migrate tiers independently

Each tier is migrated independently. This option might require more time, but it ensures that all settings are migrated to the new environment.

Parent Migration considerations

Related concepts:

Staging to production