Merging separate KX13 instances into XbyK during migration

Hi everyone,

Our team is kicking off a migration project from KX13 to XbyK where the source project.. are actually 2 separate instances of KX13 with multiple sites (each "site" is just a country-specific version of same business). Becuase each country has mostly unique content these were created in the past as multi-site rather than multi-lingual.

Codebase of both KX13 instances is mostly the same (originally cloned) with some minor tweaks here and there. And now the client wants to consolidate both into a single XbyK database AND migrate and merge content from both sources at the same time.

Both instances are in active content production, so we can't migrate once and then freeze content until the end of the project. Content migration should happen multiple times during this project.

AFAIK, the current migration tool does not cover this exact scenario so I thought about running the process like this:

  1. Migrate source 1 to XbyK
  2. Migrate source 2 to the same XbyK instance
  3. Identify collisions and problems and resolve them as customizations of source 2 migration
  4. Repeat from 1 until migrated content is stable

I wonder if someone from the community has already dealt with a similar setup and can share their approach and pitfalls?

Regards, Dmitry

Tags:
Content modeling Migration / upgrade

Answers

To response this discussion, you have to login first.