#Import schema

Import schema elements from a Hygraph project or template that you are a member of into your current project and environment. You can import models, components, remote sources, enumerations, and taxonomies without rebuilding them manually.

#When to use this feature

Use this feature when you want to:

Reuse schema patterns across projects, such as shared components, enumerations, or taxonomies.
Import specific elements instead of cloning an entire project.
Bootstrap a new project from a template or starter.
Keep shared domain models consistent across related projects.
Speed up prototyping with existing building blocks.

#What this feature does not do

It does not import elements you do not have permission to create.
It does not replace or merge your existing schema as a whole.
It does not import content entries.
It does not overwrite existing schema elements. Conflicting names must be renamed on import.

For schema export/import through the Management API or SDK, see Schema as code.

#Permissions

When you import schema elements, Hygraph respects your role's permissions. You can only import elements you have permission to create. For example, if your role lets you create models but not enumerations, Hygraph excludes enumeration elements from the list in Select elements and you can only import models.

#Get started

In Hygraph Studio, go to Schema > Import to start the import wizard.

Import schema elements

#Step 1: Select a project

Choose the Source Project to import from. The list includes:

Projects you are a member of (your current project is excluded)
Templates & Starters available to you

After you select a source, click Continue. Hygraph loads the source project's schema so you can choose elements in the next step.

#Step 2: Select elements

Hygraph only lists elements you have permission to create. See Permissions. You can browse schema elements from the source project, grouped by type:

Models
Components
Remote Sources

Enumerations
Taxonomies

You can:

Select individual elements or entire groups.
Use Select full schema to select every element that is available to import.
Search within the list to find specific elements.

Models and components often reference other schema elements. When you select an element, Hygraph automatically includes its dependencies when needed.

Plan limits: Your plan quotas apply to the import. If the selection exceeds limits for models, components, taxonomies, remote sources, or taxonomy nodes, Hygraph blocks those elements or shows a limit alert. Deselect elements or upgrade your plan until the selection fits within your quotas.

#Step 3: Resolve conflicts

If a selected element uses a display name, apiId, apiIdPlural, or remote source prefix that already exists in your current project, Hygraph treats it as a conflict.

Conflicts are resolved by renaming the schema element you are importing. Your existing schema and content are not modified. You can accept the suggested names or edit them. Related identifiers for the same element are renamed together.

You must resolve all conflicts before you can continue to review.

#Step 4: Review and confirm the import

On the review step, Hygraph calculates the import actions and shows:

The source project
How many elements will be created
Which elements will be created under a new name (Create & rename)
Any plan limit issues that still block the import

Review carefully. Changes apply to your current environment and cannot be undone automatically.

When you are ready, confirm the import. Hygraph creates the selected elements in the target environment. Newly imported elements appear in the schema sidebar when the import completes successfully.

#Import schema

#When to use this feature

Use this feature when you want to:

Reuse schema patterns across projects, such as shared components, enumerations, or taxonomies.
Import specific elements instead of cloning an entire project.
Bootstrap a new project from a template or starter.
Keep shared domain models consistent across related projects.
Speed up prototyping with existing building blocks.

#What this feature does not do

It does not import elements you do not have permission to create.
It does not replace or merge your existing schema as a whole.
It does not import content entries.
It does not overwrite existing schema elements. Conflicting names must be renamed on import.

For schema export/import through the Management API or SDK, see Schema as code.

#Permissions

#Get started

In Hygraph Studio, go to Schema > Import to start the import wizard.

Import schema elements

#Step 1: Select a project

Choose the Source Project to import from. The list includes:

Projects you are a member of (your current project is excluded)
Templates & Starters available to you

After you select a source, click Continue. Hygraph loads the source project's schema so you can choose elements in the next step.

#Step 2: Select elements

Hygraph only lists elements you have permission to create. See Permissions. You can browse schema elements from the source project, grouped by type:

Models
Components
Remote Sources

Enumerations
Taxonomies

You can:

Select individual elements or entire groups.
Use Select full schema to select every element that is available to import.
Search within the list to find specific elements.

Models and components often reference other schema elements. When you select an element, Hygraph automatically includes its dependencies when needed.

Plan limits: Your plan quotas apply to the import. If the selection exceeds limits for models, components, taxonomies, remote sources, or taxonomy nodes, Hygraph blocks those elements or shows a limit alert. Deselect elements or upgrade your plan until the selection fits within your quotas.

#Step 3: Resolve conflicts

If a selected element uses a display name, apiId, apiIdPlural, or remote source prefix that already exists in your current project, Hygraph treats it as a conflict.

You must resolve all conflicts before you can continue to review.

#Step 4: Review and confirm the import

On the review step, Hygraph calculates the import actions and shows:

The source project
How many elements will be created
Which elements will be created under a new name (Create & rename)
Any plan limit issues that still block the import

Review carefully. Changes apply to your current environment and cannot be undone automatically.

When you are ready, confirm the import. Hygraph creates the selected elements in the target environment. Newly imported elements appear in the schema sidebar when the import completes successfully.

#Import schema

#When to use this feature

Use this feature when you want to:

Reuse schema patterns across projects, such as shared components, enumerations, or taxonomies.
Import specific elements instead of cloning an entire project.
Bootstrap a new project from a template or starter.
Keep shared domain models consistent across related projects.
Speed up prototyping with existing building blocks.

#What this feature does not do

It does not import elements you do not have permission to create.
It does not replace or merge your existing schema as a whole.
It does not import content entries.
It does not overwrite existing schema elements. Conflicting names must be renamed on import.

For schema export/import through the Management API or SDK, see Schema as code.

#Permissions

#Get started

In Hygraph Studio, go to Schema > Import to start the import wizard.

Import schema elements

#Step 1: Select a project

Choose the Source Project to import from. The list includes:

Projects you are a member of (your current project is excluded)
Templates & Starters available to you

After you select a source, click Continue. Hygraph loads the source project's schema so you can choose elements in the next step.

#Step 2: Select elements

Hygraph only lists elements you have permission to create. See Permissions. You can browse schema elements from the source project, grouped by type:

Models
Components
Remote Sources

Enumerations
Taxonomies

You can:

Select individual elements or entire groups.
Use Select full schema to select every element that is available to import.
Search within the list to find specific elements.

Models and components often reference other schema elements. When you select an element, Hygraph automatically includes its dependencies when needed.

Plan limits: Your plan quotas apply to the import. If the selection exceeds limits for models, components, taxonomies, remote sources, or taxonomy nodes, Hygraph blocks those elements or shows a limit alert. Deselect elements or upgrade your plan until the selection fits within your quotas.

#Step 3: Resolve conflicts

If a selected element uses a display name, apiId, apiIdPlural, or remote source prefix that already exists in your current project, Hygraph treats it as a conflict.

You must resolve all conflicts before you can continue to review.

#Step 4: Review and confirm the import

On the review step, Hygraph calculates the import actions and shows:

The source project
How many elements will be created
Which elements will be created under a new name (Create & rename)
Any plan limit issues that still block the import

Review carefully. Changes apply to your current environment and cannot be undone automatically.

When you are ready, confirm the import. Hygraph creates the selected elements in the target environment. Newly imported elements appear in the schema sidebar when the import completes successfully.