--- title: "DNN to Xperience by Kentico Migration | ClonePartner" description: "DNN to Xperience by Kentico: Users → Custom Module Data (Object Instances): No native user object; store via custom module. Engineer-led, zero downtime." source: DNN target: Xperience by Kentico canonical: "https://clonepartner.com/migrate/dnn-to-xperience-by-kentico" --- # DNN → Xperience by Kentico migration DNN to Xperience by Kentico migration — pages, media, and taxonomies moved with content fidelity. ## Entity mappings - **Pages (Tabs)** (DNN) → **Pages (Web Pages)** (Xperience by Kentico) - **Users** (DNN) → **Custom Module Data (Object Instances)** (Xperience by Kentico) - **Roles** (DNN) → **Roles** (Xperience by Kentico) - **HTML Module Content** (DNN) → **Content Items** (Xperience by Kentico) - **Files** (DNN) → **Media Library Files** (Xperience by Kentico) - **Folders** (DNN) → **Media Libraries** (Xperience by Kentico) - **Portal (Site) Settings** (DNN) → **Channels (Websites)** (Xperience by Kentico) - **Vocabularies & Terms** (DNN) → **Taxonomies (Tag Groups)** (Xperience by Kentico) - **Permissions** (DNN) → **Roles** (Xperience by Kentico) - **Menus / Navigation** (DNN) → **Web Page Items** (Xperience by Kentico) - **URL Redirects / Aliases** (DNN) → **Custom Module / Redirect Table or IIS/Server-Level Redirects** (Xperience by Kentico) - **Scheduled Tasks** (DNN) → **Custom Modules / Module Classes** (Xperience by Kentico) - **Extensions / Modules Manifest** (DNN) → **Custom Modules / Module Classes** (Xperience by Kentico) ## Frequently asked questions ### What happens to DNN user accounts and passwords when migrating to Xperience by Kentico? DNN user accounts have no native equivalent in Xperience by Kentico, so ClonePartner stores them as object instances inside a custom module. Passwords cannot be exported from DNN or imported into Xperience by Kentico; every user will need to reset their password after cutover. Role assignments are migrated directly, so access levels are preserved even though the user objects live in a non-native location. ### Will my DNN folder hierarchy be preserved in Xperience by Kentico's media library? No — DNN folder structures flatten during migration because Xperience by Kentico uses Media Libraries rather than nested folders, and there is no direct hierarchy equivalent. Each DNN folder becomes a separate Media Library, and any nesting is lost. You should plan to reorganize your media library structure inside Xperience by Kentico after the data lands, or communicate a preferred flat naming convention to ClonePartner before the migration runs. ### How are DNN HTML module contents mapped to Xperience by Kentico, and what might look different after migration? DNN HTML module content is migrated to Xperience by Kentico Content Items, but this is an indirect mapping: the structural relationship between a module and its page is not one-to-one, so content arrives in Draft state and must be published manually before it appears on the live site. Inline links and related content references that pointed to other DNN pages or files are re-mapped during migration, but any references that relied on third-party DNN module APIs with no available endpoint will need to be reviewed and corrected by your team. Xperience by Kentico requires content items to be explicitly published after import, so a post-migration publishing step is required. ### What happens to DNN URL aliases and redirects — will SEO traffic be preserved? Xperience by Kentico has no native one-to-one equivalent for DNN's PageAlias or TabUrlAlias records, so ClonePartner handles these through a combination of two approaches: simple page-level aliases are mapped directly to the URL Slug field on the target Web Page item, while standalone redirect rules are migrated into a custom Xperience module (with SourceURL and TargetURL fields) that a lightweight ASP.NET Core middleware reads at runtime to issue 301 redirects. Alternatively, the redirect data can be exported as IIS URL Rewrite rules if your team prefers a server-level approach. Either way, your development team will need to deploy the middleware or IIS rules before the site goes live to avoid broken links. ### Do DNN scheduled tasks and custom modules migrate automatically to Xperience by Kentico? No — DNN scheduled tasks and module manifests have no equivalent native objects in Xperience by Kentico, and their logic cannot transfer because Xperience by Kentico is a full rewrite with a React-based admin and ViewComponent widget model. ClonePartner migrates the configuration data (task names, schedules, module metadata) into custom module classes in Xperience by Kentico, but the underlying application code must be rebuilt by your development team. Any third-party DNN modules that had no available API at source are flagged during scoping, since their content cannot be extracted without a resolvable endpoint. ### Are there DNN API or version requirements ClonePartner needs before starting the migration? ClonePartner requires that your DNN instance has the PersonaBar API and JWT authentication endpoint (/API/JWT/Auth/Login) accessible, as there is no single unified DNN REST API and endpoints are split across PersonaBar and legacy WebAPI services. For multi-portal DNN installations, portal context switching via request headers must be supported so each portal can be addressed separately. On the Xperience by Kentico side, Management API keys with appropriate scopes per object type must be provisioned before data can be written, and CI/CD serialization must be enabled for structural objects like forms and settings. These prerequisites are confirmed during the free 30-minute scoping call before any migration work begins. ## 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 DNN → Xperience by Kentico migration.