> ## Documentation Index
> Fetch the complete documentation index at: https://docs.acelabusa.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Exporting Revit Schedules for Import from File

> Export a schedule from Revit with the right settings so it imports cleanly into an Acelab Schedule, and fix the unmatched double quote error.

## Summary

You can export a schedule from Revit as a CSV and bring it into an Acelab Schedule with [**Import from File**](https://docs.acelabusa.com/help-center/working-on-projects/import-from-file.md). Revit's default export settings can produce a file that fails to import, most often with an **unmatched double quote** error. Choosing a few export settings in Revit prevents this.

***

## The Unmatched Double Quote Error

If your Revit export isn't set up correctly, the upload can fail with a message like this.

![Screenshot 2026 11 16 At 5 20 43 PM](https://mintcdn.com/acelab/7CTAFAGZ0QzmJGIX/images/Screenshot-2026-11-16-at-5.20.43-PM-1.png?fit=max\&auto=format\&n=7CTAFAGZ0QzmJGIX\&q=85\&s=0419ec1ea545b5bc5b1321a2d325bb7d)

**Why it happens:** Revit's default **Text qualifier** is **None**. Without a text qualifier, cell values aren't wrapped in quotes, so:

* A value with an inch mark, such as `9"`, looks like an unclosed quote.
* A value containing a comma, such as `White, Matte`, looks like two separate cells when the file is comma delimited.

Revit schedules often include both, especially in dimension, finish, and color columns.

***

## Recommended Revit Export Settings

In Revit, go to **File > Export > Reports > Schedule**, choose a location, and save the file as `.csv`. In the **Export Schedule** dialog, use these settings:

| Setting | Recommended value | Why |
| - | - | - |
| **Field delimiter** | `,` (comma) | Standard CSV format. |
| **Text qualifier** | `"` (double quote) | Wraps each cell so commas and inch marks inside values are read correctly. This prevents most import errors. |
| **Export title** | Unchecked | Keeps the schedule title out of row 1 so your column headers are the first row. |
| **Export group headers, footers, and blank lines** | Unchecked | Keeps group labels and rows like **Grand total** from coming in as extra product rows. |
| **Export column headers** | Checked | Acelab uses row 1 as headers when you assign fields. |

![Image](https://mintcdn.com/acelab/7CTAFAGZ0QzmJGIX/images/image-40.png?fit=max\&auto=format\&n=7CTAFAGZ0QzmJGIX\&q=85\&s=41ee260de36be8e863a20d14eb0f16b5)

> [!TIP]
>
> Setting **Text qualifier** to `"` (double quote) is the most important step. Revit offers `"`, `'`, and **None**; always pick `"`.

***

## If You Already Exported Without a Text Qualifier

The simplest fix is to re-export from Revit using the settings above.

If you can't re-export, you can clean the file in Excel:

1. Open the CSV in Excel.
2. Use **Find and Replace** to replace any commas inside cell values with another character, such as a dash or semicolon.
3. Choose **File > Save As** and select **CSV UTF-8 (Comma delimited)** as the file type.
4. Import the saved file into your Schedule as usual.

***

## Before You Import

Your Revit export still needs to follow the general CSV rules for Schedules: headers in row 1, one product per row, a column to map to the **Product** field, and data that matches each field's type. See [Preparing Your CSV for Import into Schedules](https://docs.acelabusa.com/help-center/working-on-projects/preparing-your-csv-for-import-into-schedules.md) for the full checklist.

***

## Outcome

With the text qualifier set to double quotes and the title and group rows excluded, your Revit schedule export uploads directly into Acelab, and each row appears as a custom product in your Schedule.
