---
title: "Xperience by Kentico to Optimizely Migration | ClonePartner"
description: "Xperience by Kentico to Optimizely: Content Items → Blocks: Reusable content maps loosely to Blocks. Engineer-led, zero downtime."
source: Xperience by Kentico
target: Optimizely
canonical: "https://clonepartner.com/migrate/xperience-by-kentico-to-optimizely"
---

# Xperience by Kentico → Optimizely migration

Xperience by Kentico to Optimizely migration — content items, media, and taxonomies moved with content fidelity.

## Entity mappings

- **Pages (Web Pages)** (Xperience by Kentico) → **Content Pages** (Optimizely)
- **Content Items** (Xperience by Kentico) → **Blocks** (Optimizely)
- **Media Library Files** (Xperience by Kentico) → **Media Assets** (Optimizely)
- **Form Definitions** (Xperience by Kentico) → **Forms** (Optimizely)
- **Form Submissions (Records)** (Xperience by Kentico) → **Forms** (Optimizely)
- **Taxonomies (Tag Groups)** (Xperience by Kentico) → **Tags** (Optimizely)
- **Taxonomy Tags** (Xperience by Kentico) → **Tags** (Optimizely)
- **Web Page Items** (Xperience by Kentico) → **Content Pages** (Optimizely)
- **Content Types (Page Types)** (Xperience by Kentico) → **Content Pages** (Optimizely)
- **Languages** (Xperience by Kentico) → **Content Languages (Language Branches) / Site Settings** (Optimizely)
- **Users** (Xperience by Kentico) → **Optimizely_CustomerContact_or_ExternalIdentityProvider** (Optimizely)
- **Roles** (Xperience by Kentico) → **Visitor Groups / Custom Roles via Membership Provider / CMS Groups** (Optimizely)
- **Channels (Websites)** (Xperience by Kentico) → **Sites / Content Roots (Optimizely CMS Sites Configuration)** (Optimizely)
- **Email Channel Templates** (Xperience by Kentico) → **Optimizely Campaign / Email Templates (via Custom Solution or Third-Party ESP)** (Optimizely)
- **Custom Module Data (Object Instances)** (Xperience by Kentico) → **Blocks** (Optimizely)

## Frequently asked questions

### Can you migrate Xperience by Kentico form submissions to Optimizely?

Form definitions migrate directly, but submission records are a workaround case on both sides: Xperience by Kentico exposes no REST endpoint for submissions, requiring direct database access or C# API calls to extract them, and Optimizely likewise has no public API for importing submission data. ClonePartner moves submission records into Optimizely's Forms storage via database-level scripting, but because the underlying schema differs, field-level validation and referential integrity checks are essential before you decommission the source system.

### Do user accounts and passwords transfer from Xperience by Kentico to Optimizely?

User account records can be migrated by seeding Optimizely's ASP.NET Identity tables (AspNetUsers, AspNetRoles, AspNetUserClaims) from Kentico's CMS_User data, but passwords cannot be carried over because Kentico's password hashing algorithm is incompatible. All users must reset their passwords after the migration, and you should plan a password-reset communication before cutover. If your organisation uses an external identity provider such as Azure AD B2C or Okta, migrating users into that IdP and pointing Optimizely at it via OIDC is the cleanest long-term approach.

### Which Xperience by Kentico objects need developer work in Optimizely before the data migration can run?

Optimizely Content Types must be defined as C# model classes and deployed before any content can be imported; ClonePartner cannot create them via API. Site definitions (mapped from Kentico Website Channels) must be registered programmatically via ISiteDefinitionRepository, and language branches must exist in Optimizely's admin or appsettings before localised content nodes are written. Roles used for CMS access control also need to be seeded into ASP.NET Identity ahead of time. ClonePartner works with your developers to confirm these prerequisites are in place before the migration run begins.

### What happens to Email Channel Templates and Custom Module Data: do they land anywhere in Optimizely?

Neither object has a direct Optimizely equivalent. Email Channel Templates are extracted from Kentico and stored as structured content in Optimizely (either as XhtmlString properties on a custom content type or as media assets) so the HTML is preserved, but dynamic Kentico macro tokens must be remapped to your target email platform's syntax (Optimizely Campaign merge tags, or your ESP's variables) by your developers. Custom Module Data is approximated as Optimizely Blocks, which preserves the structured content but not any custom admin UI or business logic; those must be rebuilt by your development team in Optimizely's React-based admin.

### Do I need professional help for this migration?

Yes. Professional help ensures proper field mapping and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.

### Does ClonePartner provide guidance before committing?

Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.

### Do you use an off-the-shelf tool to migrate from Xperience by Kentico to Optimizely, or is this built for our data?

It is built for your data. Each migration is a set of custom scripts written for your data model, not a generic import tool. That is also why we start with a sample migration: you see your own records in Optimizely before the full migration is committed.

### Can we see a sample of our Xperience by Kentico data migrated to Optimizely before the full migration runs?

Yes. We run a sample migration on your own data first, so you can review how your records look in Optimizely before the full migration goes ahead. We run validation scripts to confirm the record counts match your source, and you check the sample against your source records; if a field is missing or mapped wrong, or anything else needs adjusting, we fix it in the migration scripts and re-run the sample as many times as you need. The full migration only runs after you've approved the sample. On projects delivered in phases, each phase gets its own sample migration for you to approve.

### Will original ownership, authorship and created dates be preserved?

Yes. Created-time metadata is carried across, and ownership and authorship are carried across where the original users are set up in Optimizely. Where Optimizely cannot store one of them natively, it is kept as embedded metadata on the migrated record.

### If the new system can't natively support an old record type, what are my options?

We handle it case by case. While mapping your data, we identify every record type without a direct counterpart in Optimizely, review sample records from it and propose how it can be represented, based on what Optimizely supports: map it to the closest native object, create a custom field or object, fold it into the parent record as text or a note, attach it as a file, or keep it in a read-only archive. You choose the approach, we write the migration scripts to place the data there, so it comes across in the form you choose instead of being left behind, and you see how it looks in a sample migration before we run the full set.

### We've built custom modules and integrations on Xperience by Kentico. Can you migrate their content to Optimizely?

We migrate the content and data your custom modules hold, as long as it can be read from Xperience by Kentico programmatically. Every migration we run is written as custom code for that project rather than pushed through an off-the-shelf tool, so unusual module data is not a blocker. During scoping we review each custom module and integration with you and agree how it will be handled before any work is committed.

### Will the migration set off automations or send emails or notifications to customers, our team or anyone else?

No. Before the sample or full migration starts, we confirm with you that nothing in Optimizely will send messages about the migrated data: we import with notifications switched off wherever Optimizely allows it, and either pause any automation that could send them for the migration window or give it a condition, such as a suppression tag, that skips migrated records, which lets your live automations keep running for new records. We only proceed once you have confirmed it. If you want anyone told about the move, that message is sent separately, once the migrated data has been checked.

### Can you migrate data that Optimizely can't take in through an API?

In many cases, yes. Where something can't be written through an API, we recreate it through Optimizely's user interface where the interface allows it, and where that work is repetitive we script and automate it. We tell you up front which items are handled this way, because recreating them through the interface can add time to the schedule.

### What happens if Optimizely requires fields our Xperience by Kentico data doesn't have?

We check the destination for required fields your source data cannot fill and bring each one to you before those records are migrated. Together we agree how each one is handled, such as a mapping from an existing field, a default value, or, where Optimizely lets that field be made optional, setting it to not required for the migration so you can make it required again once the migration is complete. The migration then runs with that rule applied, so no records are rejected or left behind.

### Can you change our URL structure when we move from Xperience by Kentico to Optimizely, such as moving a blog or docs from a subdomain onto our main domain?

Yes, where Optimizely and your site's front end support the structure you want. Each page is created in Optimizely by the migration, so it can be given its new address, for example a blog moved from a subdomain to a path on your main domain, and you get a map of every old URL to its new one so redirects can be set up from the old addresses wherever they are served.

### How long does the Xperience by Kentico to Optimizely migration take?

Most migrations complete within 1–5 business days, depending on data volume and complexity; very large migrations, such as several hundred thousand records, take longer. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.

### Will there be downtime when migrating from Xperience by Kentico to Optimizely?

No. Our migration process is designed for zero downtime. Xperience by Kentico stays fully operational throughout: the bulk migration runs in the background and the cutover is fast, so there is no disruption to your live business operations.

### Can we whitelist a single IP instead of opening our network to your migration tool?

Yes. All migration traffic runs through a centralized system using one fixed IP, which your IT team can whitelist instead of opening broader network access.

### Is migration pricing a flat fee, or does it scale with data volume?

It's a flat fee with no hidden costs. The price we agree with you for your scope is the price you pay, and small variances in the final volume, a bit more or less, are included.

### How do I validate that everything migrated correctly?

Every client receives a Migration Validation Report with comprehensive metrics including record-count comparison, attachment integrity verification via checksum, and full audit logs of the migration run, showing every record created, skipped or failed. If any item didn't come across, the report names each one, the specific reason, and how to bring it across if you want it there. We also offer unlimited sample migrations, so you can check your data before the full migration runs.

### What support do you provide after the migration goes live?

At ClonePartner, we consider ourselves your partners in this journey. We take full accountability for your migration's success. Once your migration goes live, we provide 30 days of comprehensive post-migration support as standard, and longer support, such as 60 or 90 days, can be agreed for your project. During this period, we help with anything related to your migrated data, so your migration is a complete success.

### Will we get a migration report and a mapping sheet linking old record IDs to new ones?

Yes. We provide a comprehensive migration report along with an ID-mapping sheet that links each old Xperience by Kentico record ID to its new ID in Optimizely. This ensures full traceability, simplifies post-migration verification, and helps your team validate that records have been migrated accurately.

### After migration, do I contact ClonePartner or the platform's own support if something looks wrong?

ClonePartner is the contact for anything about the migrated data itself. Questions about the platform itself, such as how its features and settings work, go to the platform's own support or to whoever administers it for you.

### Will our existing Xperience by Kentico page URLs and links keep working after we move to Optimizely?

They can, through redirects and link rewriting. Links between your own pages are updated to point at their new URLs as part of the migration, and the files and images your pages use are re-hosted on Optimizely, wherever it can host them, with their links rewritten. For every old URL we give you a map to its new address, so redirects can be set up where your site is served and old bookmarks, search results and external links open the right page.

## Get a fixed-price quote

[Talk to an engineer](https://clonepartner.com/talk-to-us?duration=30&utm_source=xtoy&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click) about your Xperience by Kentico → Optimizely migration.
