---
title: Remodel page types as reusable field schemas
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

The [Xperience by Kentico: Kentico migration tool](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool) allows you to remodel your content on the fly during the upgrade process.

Using a [custom class mapping](https://github.com/Kentico/xperience-by-kentico-kentico-migration-tool/tree/master/docs/customization/Class-Mappings.md), you can discard fields, rename them, transform their values, and create [reusable field schemas](https://docs.kentico.com/documentation/developers-and-admins/development/content-types/reusable-field-schemas.md) that you can share among multiple classes.

This guide will extract common fields from two page types from **Kentico Xperience 13 (KX13)** and move them to a _Reusable field schema_ shared by both web page content types in **Xperience by Kentico (XbyK)**.

## Determine the new model

As discussed in the [migration strategy planning guide](https://docs.kentico.com/guides/upgrade-to-xbyk/upgrade-from-kx13/plan-your-strategy-for-migrating-features.md#structured-content-page-types), **page types** in KX13 map to **content types** in XbyK.

The migration tool automatically converts page types to content types with the same fields, and converts their pages to _web page items_ in the content tree of a [website channel](https://docs.kentico.com/documentation/developers-and-admins/configuration/website-channel-management.md). However, you can extend the process for specific page types, making structural adjustments as the tool converts them into content types, or changing where and how they are stored.

### Examine the source classes

In the KX13 Dancing Goat site, there are two [page types](https://docs.kentico.com/13/developing-websites/defining-website-content-structure/managing-page-types/creating-page-types.md) corresponding to coffee grinders: _Manual grinder_ and _Electric grinder_.

The _Manual grinder_ page type has the following fields:

- ManualGrinderID
- ManualGrinderPromotionTitle
- ManualGrinderPromotionDescription
- ManualGrinderBannerText

These are the _Electric grinder_ fields:

- ElectricGrinderID
- ElectricGrinderPower
- ElectricGrinderPromotionTitle
- ElectricGrinderPromotionDescription
- ElectricGrinderBannerText

### Consolidate the common fields

As both page types contain fields for a promotion title, promotion description, and banner text, we can move these fields to a shared schema.

Each content type in XbyK will need its own ID, and the electric grinder content type will need a power field that is not part of the schema.

![Diagram of grinder reusable field schema](https://docs.kentico.com/docsassets/modules/remodel-page-types/RFSUpgrade.jpg "Diagram of grinder reusable field schema")