> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/projects/project-import.md).

# Project import

Import projects in bulk from a CSV, Excel, or JSON file with AI-assisted column mapping.

Organization admins can import projects in bulk from a spreadsheet or JSON export. Cogram auto-detects and maps the columns in your file, so you don't have to match them up by hand.

Go to [Organization Settings > Projects](https://app.cogram.com/dashboard/settings/admin/projects) and click **Import**.

## Supported file formats

CSV (`.csv`), Excel (`.xlsx`), and JSON (`.json`). A downloadable example template is available on the upload page.

## Import steps

### 1. Upload

Drag a file onto the upload area or click to browse. Once a file is selected, click **Continue**.

### 2. Map Columns

Cogram auto-suggests which columns in your file correspond to Cogram project fields. Review the mappings and adjust as needed using the dropdowns. A confidence indicator shows how confident the AI is in each suggestion.

Available target fields:

| Field            | Required |
| ---------------- | -------- |
| Name             | Yes      |
| Project Number   | Yes      |
| Description      | No       |
| Client Name      | No       |
| Address          | No       |
| Owners           | No       |
| Members          | No       |
| Groups           | No       |
| Project Metadata | No       |

You can also set any column to **Skip** to ignore it. Click **Review** once the required fields are mapped.

#### Groups

A Groups cell names the groups the project belongs to. Everyone in a group assigned to a project can see that project.

List several groups separated by commas or semicolons, for example `Structural, Civil`. Add a role to a group with a colon, for example `Civil:VIEWER`. The roles are `MEMBER`, `VIEWER`, and `LEAD`. A group with no role becomes a member.

The Lead role is only available if your organization has it enabled. If a cell asks for a role that does not exist, or for Lead when it is not enabled, Cogram imports the project and shows a warning for that group.

A blank Groups cell leaves an existing project's groups unchanged. Importing groups adds them, and never removes groups the project already has.

If the project already has a group that the cell lists, the import only changes that group's role when the cell spells a role out. `Civil:MEMBER` sets the role to member. A plain `Civil` leaves the group at the role it already has, so re-importing the same sheet never changes anyone's access.

A colon with no space before the role is always read as a role. Write `Phase 1 : Design` if a group name has to contain a colon.

### 3. Review

A preview shows how many projects will be created, updated, or skipped, and lists any errors. You can also:

* **Pre-create users**: if owner or member email addresses are not yet in your organization, select which ones to pre-create and optionally send invitation emails.
* **Create groups**: if a Groups cell names a group your organization does not have, select which ones to create. Clear a group to import the projects without it.
* **Set a fallback owner**: assigned to new projects when no owner column is mapped or when mapped owners are not being pre-created.
* **Auto-file incoming emails**: optionally enable automatic email filing for imported projects.

Click **Import N projects** to proceed.

### 4. Import complete

A summary shows the number of projects created, updated, skipped, and any errors. Click **Import More** to start another import.


---

# 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.cogram.com/projects/project-import.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.
