You want to move your team’s project tracker from Coda to Notion, but the formulas that calculate budgets, deadlines, and statuses keep breaking during the transfer. Coda and Notion use fundamentally different formula languages. Coda uses a spreadsheet-like syntax with a custom function library, while Notion uses a SQL-inspired formula engine with different function names and nesting rules. This article explains exactly how to export your Coda data, set up Notion databases with matching property types, and manually rebuild each formula so the logic stays intact.
Key Takeaways: Import Coda to Notion Without Losing Formula Logic
- Coda > Export > CSV: Exports all table data as plain text, removing formulas but preserving raw values and column headers.
- Notion > New Database > Import: Creates a matching Notion database from the CSV file, generating text, number, date, and select properties as needed.
- Notion formula property: Must be created manually after import because Notion cannot read Coda formula syntax directly.
How Coda and Notion Formulas Differ
Coda formulas are written in a spreadsheet-like language that uses cell references such as [Column Name] and a large library of built-in functions like Sum(), Filter(), and DateDiff(). Coda lets you write formulas that span multiple rows and columns in a single expression. Notion formulas, by contrast, use a property-based syntax where each formula references other properties by name, such as prop("Column Name"). Notion does not support cell references or cross-row calculations in formulas; those tasks require rollups or relation properties.
Because the two formula systems are incompatible at the syntax level, no automated tool can convert a Coda formula into a working Notion formula. The only reliable method is to export the raw data from Coda, import it into Notion, and then manually rewrite each formula using Notion’s formula language. This process preserves the underlying logic and data values, even though the formula text itself must be rebuilt.
What Happens During a Direct Import
If you use Notion’s built-in CSV import feature, Coda formulas are stripped entirely. The import reads only the final computed values in each cell. For example, a Coda cell containing If([Status]="Complete", Today()-[Start Date], 0) will appear in Notion as a static number, such as 14. The formula logic is lost. You must recreate that logic in Notion’s formula editor after the import.
Steps to Export From Coda and Import Into Notion
Follow these steps exactly to move your data without corruption. Do not attempt to copy and paste individual cells; that method loses all formula values and often breaks column types.
- Open the Coda table you want to export
Navigate to the Coda document and open the specific table that contains the formulas you need to preserve. Make sure the table is in grid view, not a detail or card view, so all rows and columns are visible. - Export the table as CSV
In Coda, click the three-dot menu in the upper-right corner of the table. Select Export > CSV. A file with the.csvextension downloads to your computer. This file contains all raw cell values — numbers, dates, text, and select options — but no formulas. - Open Notion and create a new database
In Notion, navigate to the page where you want the imported data to appear. Type/tableand select Table — Inline to create a blank database. Alternatively, use/databaseand choose Database — Inline. Name the database to match the original Coda table. - Import the CSV file into the Notion database
Click the three-dot menu in the upper-right corner of the new Notion database. Select Import and choose CSV. Select the CSV file you downloaded from Coda. Notion will map each column to a property type. Review the mapping and adjust any mismatches. For example, if a column contains dates, make sure Notion assigns the Date property type, not Text. Click Import to complete the process. - Verify that all data rows and columns are present
After the import, count the rows and columns in Notion and compare them to the original Coda table. Check that numeric values, dates, and select options appear correctly. If any data is missing, re-export the Coda table and repeat the import. Do not proceed to formula rebuilding until the raw data is accurate. - Add a formula property for each Coda formula you need to recreate
In the Notion database, click the + button in the last column header. Select Formula from the property type list. Name the formula property to match the original Coda column name. You must create one formula property per Coda formula column. Repeat this step for every formula you want to preserve. - Write the Notion formula equivalent
Click the formula property header and select Edit property. In the formula editor, rewrite the Coda logic using Notion’s formula syntax. For example, a Coda formula that calculates days since a start date:Today() - [Start Date]
becomes in Notion:dateBetween(now(), prop("Start Date"), "days")
Refer to Notion’s formula documentation for function equivalents. Test each formula on a single row first by checking the computed value matches the original Coda result. - Test all formulas across multiple rows
After writing each formula, scroll through the database to verify that the computed values are correct for different data scenarios. Check edge cases such as empty cells, zero values, and dates in the past or future. Fix any formula errors by editing the formula property again.
Common Formula Conversion Challenges and Solutions
Coda If() Logic Does Not Work in Notion
Coda uses If(condition, value_if_true, value_if_false). Notion uses a similar but slightly different syntax: if(condition, value_if_true, value_if_false). The difference is case sensitivity — Notion expects lowercase if. Also, Notion does not support nested If() beyond about five levels. If your Coda formula contains deeply nested conditions, break them into multiple formula properties or use Notion’s ifs() function, which evaluates multiple conditions sequentially.
Date Calculations Produce Different Results
Coda’s DateDiff() function returns the difference between two dates in a specified unit. In Notion, use dateBetween(endDate, startDate, "unit"). The unit must be a string: "days", "hours", "minutes", "months", or "years". Coda defaults to days if no unit is specified, but Notion requires the unit argument. Always include the unit string to avoid errors.
Lookup and Cross-Table References Break Completely
Coda allows formulas that reference cells in other tables using ThisTable.[Column] or OtherTable.[Column]. Notion does not support direct cross-table cell references in formulas. Instead, you must create a relation property between the two databases and then use a rollup property to pull the value into your formula. For example, to reference a value from a “Projects” database in a “Tasks” database, add a relation column in Tasks that links to Projects, then create a rollup in Tasks that displays the desired Projects property. Finally, reference that rollup property in your formula using prop("Rollup Name").
Coda vs Notion Formula Capabilities Compared
| Feature | Coda | Notion |
|---|---|---|
| Formula syntax | Spreadsheet-like with cell references | Property-based with prop() function |
| Cross-table references | Direct cell references in formulas | Requires relation + rollup properties |
| Nested conditionals | Unlimited nesting | Limited to approximately 5 levels of if() |
| Date difference function | DateDiff(date1, date2, unit) | dateBetween(date1, date2, “unit”) |
| Array functions | Filter(), Find(), Unique() | No native array functions; use rollup and formula combinations |
| Formula import from CSV | Not supported | Not supported; formulas must be rewritten |
You can now move your Coda documents into Notion while keeping all formula logic intact by following the export-import-rewrite workflow. Start by exporting your most important Coda table and rebuilding its formulas in Notion one at a time. Use Notion’s formula editor’s built-in function reference by typing / inside the editor to see available functions. For complex multi-table formulas, create relation and rollup properties before writing the final formula.