> 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/email/importing-emails.md).

# Importing emails

Import historical project emails from an Outlook archive (.pst), individual email files (.eml), or Outlook message files (.msg) into a Cogram project.

Bring existing project emails into a Cogram project. Organization admins import an Outlook archive (`.pst`) themselves. Anyone who can file emails to a project can upload a few `.eml` or `.msg` files. Imported emails appear in the project's **Emails** tab alongside any live-filed correspondence and are available as context for the AI agent.

## Supported formats

| Format             | Extension | How to import                                           |
| ------------------ | --------- | ------------------------------------------------------- |
| Outlook archive    | `.pst`    | [Import an archive](#import-a-pst-archive) (org admins) |
| Email message file | `.eml`    | [Upload email files](#upload-email-files)               |
| Outlook message    | `.msg`    | [Upload email files](#upload-email-files)               |

## Import a PST archive

A `.pst` archive is the most efficient format for large imports. Only organization admins can import one.

**Before you start**

* Export the archive from Outlook. See [Exporting a PST from Outlook](#exporting-a-pst-from-outlook).
* Pick a shared project to receive the emails. You can't import into a personal project (My Workspace).
* Your organization can run one import at a time.

**Steps**

1. Open [Organization settings → Email](https://app.cogram.com/dashboard/settings/admin/email#email-archive-import) and go to **Import email archive**.
2. Pick the project.
3. Choose the `.pst` file. Use one file, up to 5 GB.
4. Click **Import emails** and confirm in the dialog.
5. Keep the tab open while the file uploads. If the upload stops, choose the same file again to continue.

When the upload finishes, Cogram imports the emails in the background. You can close the tab at that point.

**What good looks like**

The import list shows a row for the archive with a status: **Pending**, **Importing**, **Completed**, or **Failed**. It also shows these counts:

| Count          | Meaning                                                                                                                                                                                                  |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Imported**   | Emails added to the project.                                                                                                                                                                             |
| **Duplicates** | Emails already in the project. Importing the same file again adds nothing twice.                                                                                                                         |
| **Skipped**    | Calendar items, contacts, tasks, notes, emails with no sender, recipient, or date, and emails older than your organization's [email retention period](https://docs.cogram.com/email/email-retention.md). |
| **Errors**     | Emails Cogram couldn't read or file. Click **View errors** to see them. The list shows the first 1,000.                                                                                                  |

**What to expect**

* Cogram imports every folder, including Deleted Items. Review the archive before you import it.
* Project members can see the imported emails.
* Automations that run when an email is filed don't run for archive emails.
* Attachments over 100 MB each are left out, as are attachments past 200 MB in total per email. An email attached to another email is also left out. The row shows how many.
* Only the Outlook **Confidential** category carries over. Cogram doesn't check archive emails for confidential content, so review sensitive mail before you import it.
* Cogram deletes the uploaded file from its storage when the import ends.
* There is no one-step undo. Check the project and the archive before you click **Import emails**.

## When to contact support

Contact your Cogram representative or email **<support@cogram.com>** when you need to import:

* A `.pst` archive over 5 GB
* A `.zip` of `.eml` or `.msg` files
* A Newforma export
* Another format, or many projects at once

Include:

* The files (attached or as a secure download link)
* The Cogram project name or project ID
* Your Cogram user email address

One import request = one project. For multiple projects, submit one request per project.

Emails already in the project (matched by Message-ID) are skipped automatically.

## Upload email files

You can upload emails yourself when you are the project's Owner, or an Org Admin or Org Owner, and you have an [Email Management](https://docs.cogram.com/organization-administration/licensing.md) seat. Org Admins and Org Owners can't upload into a colleague's personal project.

1. Open the project from the [Projects page](https://app.cogram.com/dashboard/projects) and go to its **Emails** tab. You can also use the **Emails** page with one project picked at the top.
2. Click **Upload emails**.
3. Drag `.eml` or `.msg` files into the window, or click **browse** to choose them. You can upload up to 20 files at a time, 25 MB each.
4. Check the emails. Each file shows its subject, sender and date, and **Already in project** when the project has it. Click the arrow to see the recipients, attachments and the start of the text. Click **×** to leave a file out.
5. Click **Upload**.

Each file shows its result: **Filed** (click it to open the email), **Already in project**, or **Failed** with the reason. Emails keep their original sent date, so older emails appear further down the list.

An uploaded email works like a filed one:

* It belongs to the first sender or recipient who has a Cogram account in your organization, or to you when none does. You are recorded as the person who filed it.
* The text of its PDF and Word attachments is searchable and available to Agent.
* It starts your organization's automations that run when an email is filed, even when the email is years old.
* It isn't turned into an RFI or submittal, and isn't added to one. Mail filed from a mailbox can be; an uploaded file never is.

If your organization has [**Hide confidential email from project members**](https://docs.cogram.com/email/confidential-email.md#turn-hiding-on-or-off) on, an uploaded email is filed as confidential when:

* the organization already holds the same message as confidential, or Cogram flagged it as possibly confidential when it was filed from a mailbox, or
* the file has the Outlook category **Confidential** (`.msg`), or the same word in its Keywords header (`.eml`). **Confidential Archive** marks it Confidential Archive when your organization has Confidential Archive, and Confidential otherwise. A category counts only when every other copy of the message is in a project you can mark confidential.

### If a file fails

| Message                                                                                           | What to do                                                                                         |
| ------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| Only .eml and .msg files can be uploaded.                                                         | Save the email from your mail app as `.eml` or `.msg`, and upload that file.                       |
| This file is over 25 MB. Files up to 25 MB can be uploaded.                                       | Remove large attachments from the email, or [contact support](#when-to-contact-support).           |
| Couldn't read this file. It may be damaged. Export it from your mail app and upload the new file. | Export the email from your mail app again and upload the new file.                                 |
| Another upload of this email is still running. Upload it again in a moment.                       | Wait a moment, then click **Retry failed**.                                                        |
| Couldn't preview this file. You can still upload it.                                              | The preview didn't load. Upload the file anyway; if it fails, the row shows why.                   |
| Couldn't upload this file. Retry it, or contact <support@cogram.com> if it keeps failing.         | Check your connection and click **Retry failed**. If it fails again, contact <support@cogram.com>. |

## Exporting a PST from Outlook

1. Go to **File → Open & Export → Import/Export**.
2. Select **Export to a file → Outlook Data File (.pst)**.
3. Select the account or folder to export. Check **Include subfolders** for a full export.
4. Choose a save location and click **Finish**.

## Next steps

* [Emails](https://docs.cogram.com/email/emails.md): forward or auto-file ongoing project correspondence
* [Outlook add-in: email filing](https://docs.cogram.com/email/outlook-add-in-email-filing.md): connect Outlook to file emails automatically going forward
* [Agent](https://docs.cogram.com/agent/agent.md): use imported email history to generate summaries and reports


---

# 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/email/importing-emails.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.
