Migration fails when field already exists

2025/08/28 6:45 PM

I'm working through a migration from KX13 to XbyK 30.8.0 and I'm stuck on migrating content into a database that was started prior to the data migration. All the version info, site name, etc match.

We have a content type called Page. In my migration code, I'm adding this content type definition and field mapping and setting values based on data being migrated. When I run the migration process, it's now erroring out saying the "the field name is already taken. Content type field names must be unique within the current content type and across all reusable field schemas."

Is importing content into an existing content type not allowed?

Environment

  • Xperience by Kentico version: [30.8.0]

  • .NET version: [9]

  • Execution environment: [Private cloud Azure]

Tags:
Content types Migration / upgrade v30.8.0

Answers

2025/09/26 5:14 PM

Hi Brenden,

Were you able to resolve your issue? If not, quick clarifying question to better understand your problem:

Is the Page content type existing in your XbyK prior to running the migration? - You mention a migration into an existing content type, but you're also saying you're adding the content type definition during the data migration process.

I wonder if this might be causing you the conflict - that you're trying to define content type or its fields that already exist.

Generally speaking, you should be allowed to import content into an existing content type.

2025/09/30 8:42 PM

Dominika,

Specifically, the issue is with categories/taxonomy. When I do the initial migration and migrate KX13 categories, it creates the taxonomy and reusable schema, then assigns that reusable schema to the content type. When I run the --pages import again by itself, with the --bypass-dependency-check flag enabled, it complains and says the field category_legacy already exists.

To response this discussion, you have to login first.