Hi all,
We're planning a **content-only migration from Kentico 12 to Xperience by **
Kentico and have a somewhat unique requirement: we don't need a full
migration. We only need to bring over a specific subset of content types, and
only items created or modified from a certain date onward (not the full
history).
Our target XbyK environment already has an existing solution in place with its
own content, so we need to be careful not to overwrite or delete anything
that's already there.
I have a few questions I'm hoping the community can help with:
1. Has anyone done a partial / scoped migration like this before?
Specifically — migrating only a defined list of content types from K12 to
XbyK, filtered by date, rather than doing a full migration. I'd love to hear
about your experience and any lessons learned.
2. What's the best approach to narrow the migration scope?
We want to include only a specific set of content types and only items from a
given date forward. Is this best handled through:
- Configuration/filtering options in the Kentico Migration Toolkit?
- Custom SQL queries or data extraction on the K12 side before running the
migration?
- Some other approach?
What has worked well (or not) for limiting scope?
3. Are there any gotchas or things to watch out for?
Thinking about things like:
- Orphaned references or broken relationships when you only migrate a subset
- Dependencies between content types that might not be obvious
- Media/attachment handling when the related page types aren't included
- Tree structure / page hierarchy considerations
- Anything else that bit you during a partial migration
**4. How to integrate migrated items into an existing XbyK solution via **
Continuous Delivery without overwriting existing content?
Once the migration is complete in a staging XbyK instance, we need to bring
those items into our existing production solution. Our current workflow uses
Continuous Delivery (CD) for deployments. What's the safest way to:
- Export only the newly migrated items from the staging instance
- Import them into the existing solution via CD
- Ensure nothing already present gets overwritten or deleted in the process
Is CD's restore mode the right fit here, or is there a better pattern for
merging net-new content into an existing environment?
---
Environment:
- Source: Kentico 12
- Target: Xperience by Kentico (31.3.0)
- Migration scope: Content only (no custom code, templates, or site settings)
- Deployment: Continuous Delivery
Thanks in advance for any guidance or shared experience!