> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/organizations/importing-an-organization.md).

# Importing an organization

Use this when a **separate i3D account belongs to your company** and you want it to become part of your organization — the classic case being a company that has accumulated several i3D accounts over the years, or a studio being brought under a publisher's structure.

Importing is also referred to as merging or combining organizations.

{% hint style="info" %}
Importing is available to organization **admins**. If you aren't an admin you'll see the organization structure, but not the **Import organization** button.
{% endhint %}

## To import an organization

{% stepper %}
{% step %}

#### Open the Overview page

Go to **Organization Management → Overview**.
{% endstep %}

{% step %}

#### Start the import

In the **Organization Structure** panel, click **Import organization**.
{% endstep %}

{% step %}

#### Identify the organization

Enter the **owner email** of the organization you want to bring in — the person who owns that i3D account.
{% endstep %}

{% step %}

#### Choose where it lands

Choose the **destination organization** — where in your structure it should sit.
{% endstep %}

{% step %}

#### Confirm

Read the warning, then click **Import organization**.
{% endstep %}
{% endstepper %}

An invitation is sent to that owner. **Nothing happens until they accept.** The request appears on the **Invitations** tab with the **Core** membership label — the marker that sets an import request apart from an ordinary invitation — and you can resend or withdraw it from there.

## What happens when they accept

* Their **members and servers move into** the destination organization you chose.
* **Their organization disappears** from the Console as a separate entry — it no longer shows in the organization switcher or the structure tree.
* The owner of the imported organization appears in your Members list with the **Core** membership label.
* Each server keeps showing its **original account number** in the *Billing Account* column on the [Servers page](/organizations/servers-page.md), so you can always tell which account a server actually belongs to.
* **Billing does not change.** Each account carries on receiving its own invoices exactly as before. Billing is not yet organization-aware — see [Organizations](/organizations.md) for what that means today.

## Reversing an import

{% hint style="warning" %}
You can't reverse an import yourself in every case. If you need to cancel or reverse a merge, contact i3D.net support and we'll do it for you.
{% endhint %}

## When an import will be refused

You'll get a clear message if the import can't go ahead — for example:

* The organization has already been merged into another one.
* The organization is above yours in the structure (merging it would create a loop).
* The combined structure would exceed the depth or width limits — raise a support case if you need those increased.

## Related topics

* [Inviting a member](/organizations/inviting-a-member.md)
* [Accepting an invitation](/organizations/accepting-an-invitation.md)
* [Members](/organizations/members.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.i3d.net/organizations/importing-an-organization.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.