Migrate from Coda to Asana

Each Coda Doc maps to an Asana Project. We extract the Doc title, creation timestamp, and owner, then create a corresponding Asana Project with the same name and set the Asana Project start and due dates from any date controls found in the Doc. Nested child Docs map to sub-projects or, if the destination is a single workspace, to Projects tagged with a custom field indicating the original Doc hierarchy level.

Coda Pages nested inside a Doc map to Asana Sections within the target Project. We preserve the page tree depth by creating a Section for each top-level and second-level Page, and we attach a page-order custom field so the admin can verify sequence in the destination. Pages that contain only sub-pages without tables map to empty Sections as placeholders for the navigation hierarchy.

Each Coda Table inside a Doc maps to a group of Asana Tasks, one per row. The table name becomes an Asana Section or a tag on the Tasks. Each Coda column becomes an Asana custom field: text to Text, number to Number, date to Due Date, select to Enum (single-select picklist), multi-select to Enum (multi-select), and relation columns to Asana Dependencies or a Text field holding the target Row ID reference.

We extract the full column definition per table — type, options list, display formula — before mapping. Coda text, number, date, checkbox, and select columns map directly to Asana Text, Number, Due Date, Checkbox, and single-select custom fields. Coda formula columns resolve to their computed value at migration time and store the result as a Number or Text custom field; the formula logic itself is flagged as non-migratable. Select and multi-select options migrate as Enum option values in Asana.

Coda rows map to Asana Tasks. We preserve the Coda Row ID as a custom field coda_row_id__c for audit and reference back to the source. Every column value maps to the corresponding Asana custom field by name match or explicit mapping. Task assignee resolves by matching the Coda row collaborator to an Asana User by email. Rows without an assigned collaborator create unassigned Tasks.

Coda's Relation column type links rows across tables within a Doc. We extract the source Row ID and target Row ID, then look up the corresponding Asana Task GIDs in the migrated task map. The resolved Asana Task GIDs populate the dependency field (Depends On) on the source Task. Cross-doc relations that reference rows in different Coda Docs map to project-level task dependencies with the external Project GID recorded in a custom field.

Coda attachments stored in rows are fetched directly from the Coda API using an authenticated session before any CSV staging step, which bypasses the URL expiration issue that affects CSV-passing migrations. The file is uploaded to Asana and attached to the corresponding Task via the Asana Attachments API. We handle the upload order so that attachments are associated with tasks whose parent records already exist in Asana.

Coda automation rules (trigger + conditions + actions scoped to a Doc) do not replay in Asana because Asana Rules use a different trigger/action model. We export every automation rule definition — trigger type, condition list, and action list — and deliver a written inventory mapping each Coda automation to a recommended Asana Rule configuration or Zapier/Make automation. The admin rebuilds these post-migration.

Coda formula columns compute values dynamically at display time. We evaluate each formula against the row data at migration time and store the resulting value as a static Text or Number custom field in Asana. Formulas that reference other columns in the same table compute cleanly; formulas that reference rows in other tables resolve the reference using the migrated Row ID map before computing. Formulas that use cross-doc lookups are flagged as complex and stored as read-only text with a note for manual verification.

Coda canvas text blocks, embeds, and inline images outside of tables are extracted as structured content blocks. We map text sections to the Asana Project description or Notes field for short content, and flag longer canvas blocks as requiring a companion Google Doc or Notion page for the non-tabular narrative content. Complex nested canvas layouts with multiple embedded tables require manual reorganization in Asana.

Coda user identity (names, @mentions, collaborator assignments) maps to Asana Users by email address. We extract every distinct Coda user email from row collaborators and page owners, then match against the Asana destination workspace User list. Users without a matching Asana account go to a reconciliation queue for the admin to provision before task import. Comments and @mentions themselves do not migrate because Coda's comment API does not expose user identity data.

Coda Packs are native API integrations that connect Coda tables to external data sources (Jira, Salesforce, Slack, and 600+ others). They execute in Coda's runtime environment and cannot be exported or replayed in Asana. Every Pack in use is documented during discovery with a recommendation for replacement: Asana's native App integrations, Zapier, Make, or a custom API connection. The admin rebuilds data connections post-migration.