---
title: "KB: Understanding the Migration from Field Layout Schemes to Field Schemes"
canonical: "https://support.appfire.com/space/SUPPORT/3216478849/KB%3A%20Understanding%20the%20Migration%20from%20Field%20Layout%20Schemes%20to%20Field%20Schemes"
format: markdown
---
## Overview

Atlassian are changing how Jira Cloud manages field configurations. As part of this evolution, **Field Layout Schemes** and **Field Layouts** are being replaced by a unified **Field Scheme** model.

To ensure your configuration management remains seamless, CMJC automatically handles this transition when you deploy snapshots. This article explains how your legacy field configurations are converted into the new Field Scheme format during the migration process.

> ℹ️ **See Atlassian’s  Announcement for more information on what’s changing:**  
> ℹ️ [https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Say-goodbye-to-field-configuration-schemes-and-hello-to-the/ba-p/3160315?referer=https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Say-goodbye-to-field-configuration-schemes-and-hello-to-the/ba-p/3160315](https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Say-goodbye-to-field-configuration-schemes-and-hello-to-the/ba-p/3160315?referer=https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Say-goodbye-to-field-configuration-schemes-and-hello-to-the/ba-p/3160315)** **

## How CMJC will handle Field Layout Schemes

As far as snapshot creation and Server To Cloud export, CMJC will keep on exporting the configuration as is. If the Jira instance used Field Layouts and Field Layout Schemes hey will still be exported as usual. CMJC will also export Field Schemes if the Jira Cloud Instance has been migrated to use those.

When performing analysis from an instance that supports <u>**Field Layout Schemes**</u> to another one that still supports <u>**Field Layout Schemes**</u>, there will be no difference in the way things are handled.

When performing analysis from an instance that supports <u>**Field Layout Schemes**</u>** **to another one that has been migrated to <u>**Field Schemes**</u>**, **CMJC will convert 1:1 the exported Field Layout Schemes to Field Schemes.

CMJC performs the following logic to create the new Field Schemes:

### 1. Mapping Field Properties

For every field included in your legacy Field Layouts, a corresponding entry is created in the new Field Scheme.

- **Default Configuration:** If a Field Layout was set as the "Default" in your legacy scheme, its settings (e.g., whether a field is **Required** and what its **Description** is) are migrated as the primary parameters for that field in the new Scheme.
- **Issue Type Overrides:** If you had specific Field Layouts mapped to specific **Issue Types** (e.g., a special layout for "Bugs"), those settings are migrated as "Issue Type Overrides" within the new Field Scheme.

### 2. Preserved Metadata

To ensure continuity and ease of auditing, the following attributes are preserved during the conversion:

- **Name:** The name of your Field Layout Scheme is carried over to the Field Scheme.
- **Description:** Any existing description is maintained.

## Key Differences & Limitations

While we strive for a 1:1 functional migration, Jira Administrators should be aware of the following:

- **Issue Type Restrictions:** The legacy Field Layout configuration did not have a direct concept of "restricting" a field's existence to a specific issue type (it only controlled visibility/requirement within a layout). Therefore, the "Restricted to Issue Type" setting in the new Field Scheme will remain blank by default. The field will behave as it did previously, governed by its visibility and requirement settings.
- **Field Optimisation**: Due to limitations of the selected Scope, CMJC can not perform optimisation of fields based on their usage. As such all fields used in the original Field Layout Scheme will be associated with the new Field Scheme.