Skip to content

Latest commit

 

History

History
93 lines (83 loc) · 9.49 KB

Supported-Data.md

File metadata and controls

93 lines (83 loc) · 9.49 KB
Raw

Supported Data

The Kentico Migration Tool does not transfer all data available in the source instance. Xperience by Kentico currently provides a smaller, more focused set of features. As a result, some objects are discarded or migrated to a suitable alternative.

This tool only supports content and objects stored in the database and related binary data on the file system, such as media library files. Code, customizations, and any other types of content need to be migrated manually to the target project and adjusted for Xperience by Kentico.

Currently, the Kentico Migration Tool supports the following types of data:

  • Sites

    • The tool migrates each site on the source to a website channel object in Xperience by Kentico.

  • Cultures

    • The set of cultures used across all sites in the source gets mapped to a language in the Languages application.

  • Content types (Page types in earlier Kentico versions)

    • The Kentico Migration Tool attempts to map the Data type and Form control of page type fields to an appropriate equivalent in Xperience by Kentico. This mapping is not always possible and does not work for custom data types or form controls. We recommend checking your content type fields after the migration and adjusting them if necessary.
    • The migration includes only page types assigned to at least one site on the source instance.
    • Xperience by Kentico currently does not support:
      • Macro expressions in page type field default values or other settings. Content type fields containing macros will not work correctly after the migration.
      • Categories for page type fields. Field categories are not migrated with page types.
      • Page type inheritance. Page types that inherit fields are migrated including all inherited fields but the binding to the parent page type is not preserved.
    • All migrated Content types have the Include in routing option enabled (the migration never creates pages without URL and routing).

  • Pages

    • The migration includes the following versions of pages:
      • Published
      • Latest draft version - for published pages, the version is migrated to the Draft status; for pages that do not have a published version, the version is migrated to the Draft (initial) workflow step.
      • Archived pages are migrated to the Unpublished status.
    • Each page gets assigned under its corresponding website channel.
    • Linked pages are currently not supported in Xperience by Kentico. The migration creates standard page copies for any linked pages on the source instance.
    • Page permissions are currently not supported by the Kentico Migration Tool and are not migrated. If you need page ACLs to be migrated, please open an issue and request the feature.
    • Migration of Page Builder content is only available for Kentico Xperience 13.
      • If you are migrating a Kentico 12 MVC application you can upgrade it to Kentico Xperience 13 using the Kentico Installation Manager (KIM) and then upgrade to Xperience by Kentico with Page Builder content.

  • Page attachments

    • Page attachments are not supported in Xperience by Kentico. Attachments are migrated into media libraries. See Migration.Tool.CLI/README.md - Attachments for detailed information about the conversion process.

  • Preset page templates (Custom page templates in Kentico Xperience 13)

    • Migration of custom page templates is only available for Kentico Xperience 13.

  • Categories

  • Media libraries and media files

    • Media library permissions are currently not supported in Xperience by Kentico and are not migrated.

  • Forms

    • The migration does not include the content of form autoresponder and notification emails. You can migrate form autoresponders to Xperience by Kentico manually by copying your HTML code and content into Email templates and Emails. See Emails.

  • Users

    • Xperience by Kentico uses separate entities for users with access to the administration interface (CMS_User table) and live site visitor accounts (CMS_Member table). Consequently, only users whose Privilege level is Editor or higher are migrated (Users -> edit a user -> General tab).
    • Users in Xperience by Kentico must have an email address. Migration is only supported for users who have a unique email address value on the source instance.
    • Custom user fields are an optional part of module class migration.
    • Live site users are represented using a separate Member entity and stored in the CMS_Member table. The migration identifies live site users as those without access to the administration interface - accounts with Privilege level set to None (Users -> edit a user -> General tab).

  • Roles

    • Only roles that have at least one user whose Privilege level is set to Editor and above are migrated.
    • Because Xperience by Kentico uses a different permission model, no existing role permissions or UI personalization settings are migrated. After the migration, the permissions for each role must be configured again.

  • Contacts

    • The target instance's OMContact and OMActivity database tables must be empty for performance reasons.
    • Custom contact fields are an optional part of module class migration.

  • Activities

  • Consents and consent agreements

  • Modules and classes

    • The migration includes the following:
      • Custom modules
      • All classes associated with custom modules
      • All data stored within custom module classes
      • The following customizable system classes and their custom fields: User, Media file, Contact management - Account (however, accounts are currently not supported in Xperience by Kentico), Contact management - Contact
    • Module and class migration does NOT include:
      • UI elements and all related user interface settings. The administration of Xperience by Kentico uses a different technology stack than earlier Kentico versions and is incompatible. To learn how to build the administration UI, see Extend the administration interface and Example - Offices management application.
      • Alternative forms under classes and UI-related configuration of class fields (field labels, Form controls, etc.). After the migration, you must manually create the appropriate UI forms in Xperience by Kentico.
      • Custom settings under modules, which are currently not supported in Xperience by Kentico
      • Module permissions (permissions work differently in Xperience by Kentico - see Role management and UI page permission checks)
      • As with all object types, the Kentico Migration Tool does not transfer code files to the target project. You must manually move all code files generated for your custom classes (Info, InfoProvider, etc.).

  • Custom tables

    • Custom tables are not supported in Xperience by Kentico. Data from custom tables is migrated to the target instance as custom modules.
    • The migration only transfers data from custom tables to the custom module (CMS_Resource) database table.
    • Any user interface, listings, filters, and other functionality related to migrated custom tables needs to be implemented in the target instance.

  • Setting values

    • The migration only transfers the settings that exist in Xperience by Kentico.
    • The migration excludes site-specific settings that do not have a corresponding website channel-specific alternative in Xperience by Kentico.

  • Countries and states

Unsupported data

The following types of data exist in Xperience by Kentico but are currently not supported by the Kentico Migration Tool:

  • Contact groups
    • Static contact groups are currently not supported in Xperience by Kentico.
    • The condition format for dynamic contact groups is not compatible. To migrate contact groups:
      1. Migrate your contacts using the tool.
      2. Create the contact groups manually in Xperience by Kentico.
      3. Build equivalent conditions.
      4. Recalculate the contact groups.
  • License keys
    • Xperience by Kentico uses a different license key format.

Additionally, object values or other content with Macros will not work correctly after the migration. Macro expressions are currently not supported for most data in Xperience by Kentico.