Testing link behavior between spaces after batch migration in Confluence Data Center

[Khammampati Surendra]

We are in the process of migrating spaces between two Confluence Data Center instances (source and target).
The migration is being done in two batches:

• Batch 1: 100 spaces migrated to the target instance this week.

• Batch 2: The remaining 100 spaces will be migrated to the target instance next week.

Problem:

Some spaces in Batch 2 (not yet migrated) contain links to spaces in Batch 1 (already migrated). Once Batch 1 spaces are in the target instance, links from Batch 2 spaces pointing to Batch 1 will not work until Batch 2 is also migrated.

Question:

Is there a way to configure Confluence such that if a link points to a non-migrated space, the link would automatically redirect back to the source instance until the space is migrated to the target instance?

This would ensure that users can access all linked content seamlessly during the migration process.

Environment:

• Confluence version: 8.5.15

• Deployment: Data Center  

Looking forward to your insights or recommendations on how to handle this scenario.

[Shawn Doyle - ReleaseTEAM]

There is no way from inside Confluence to achieve this.

However, you could set up an HTTP redirect to redirect traffic to the new server for the sub-set of spaces.  This requires installing a HTTP server in front of your confluence server, configuring rules for each space and probably dealing with SSL keys.

This may seem too daunting for just a week of traffic.