Migrate from Spreadsheet.com to Asana

A Spreadsheet.com Workbook maps to an Asana Team as the organizational container, with each Sheet inside the Workbook mapped to a separate Asana Project under that Team. We use the workbook manifest to enumerate Sheets, then create corresponding Asana Projects in the destination Team, preserving the workbook's original name as the Team name. If the workbook contained cross-sheet row references or linked data, we flag these as lookup-resolution items requiring customer review during sandbox validation.

Each Sheet within a Spreadsheet.com Workbook maps to a single Asana Project. Column headers from the Sheet become the starting point for custom field definitions in the Asana Project. Sections within the Sheet (identified by delimiter rows or section columns) map to Asana Sections within the Project, which provides the closest structural analog. We parse the Sheet's column type metadata to inform the custom field type selection in Asana.

Spreadsheet.com Rows map to Asana Tasks within the parent Project. The row's primary text content maps to Task Name; the row's column values map to Task fields (standard fields for dates and assignees, custom fields for non-standard column types). Multi-select cell values are stored as comma-separated text in the custom field and noted for manual conversion to Asana multi-select after migration. Date columns map to Start Date or Due Date in Asana (Due Date is available in Free; Start Date requires Premium).

Spreadsheet.com columns of type text, number, currency, and date map directly to Asana standard fields or custom fields of the matching type. Date columns with valid ISO or US-format dates migrate as Due Date or Start Date. Assignee columns containing email addresses map to Asana assignee if the corresponding user exists in the destination Asana workspace; otherwise, the email address is stored in a text custom field for manual assignment after user provisioning.

Spreadsheet.com multi-select columns (checklist-style cell values) map to Asana custom fields of type Multi-select. User picker columns map to Asana people custom fields. Because Spreadsheet.com allowed multiple users in a single cell and Asana's people custom field supports multiple selections, the mapping is direct when the emails are valid Asana workspace members. If the emails do not match existing Asana users, we store them as text for manual resolution. Premium plan is required for custom fields in Asana; we flag this requirement at scoping.

Formula-computed columns in Spreadsheet.com evaluate server-side and export as static text or error values. We extract the computed result as a text string and place it in a custom field labeled with the original column name and suffixed '(computed)'. The formula logic itself is not preserved. We document all formula columns during discovery so the customer's admin can rebuild computed fields as Asana custom formula fields or dependent field logic in Asana Rules where applicable.

Spreadsheet.com Kanban views group rows by a status or category column. We infer the grouping column from the Kanban configuration and apply the same grouping in Asana's Board view, using the mapped column's values as swimlane headers. Filtering and column ordering from the Kanban view are documented as Board configuration settings to apply post-migration. The view type itself is set per-project in Asana.

Spreadsheet.com Gantt views use start-date and end-date columns to render bar charts. We identify the date range columns, then configure Asana's Timeline (Gantt) view with the same Start and Due Date field assignments. Dependencies between rows in Spreadsheet.com are inferred from dependency columns or linked-row references and mapped to Asana task dependencies (Successor/Predecessor) using the Asana dependencies API.

Spreadsheet.com Calendar views render rows on a date grid using a designated date column. We configure Asana Calendar view on the same project using the mapped Due Date or a custom date field as the calendar anchor. Recurring event patterns from Spreadsheet.com do not migrate; we document recurring configurations for manual rebuild in Asana Rules with a scheduled trigger if applicable.

Spreadsheet.com Card views display rows as card widgets, often with image or attachment previews. We map Card views to Asana Board view, preserving the grouping column and the card-style layout intent. Image and attachment previews in Spreadsheet.com cards become task attachments in Asana, viewable from the task detail pane.

Spreadsheet.com web form submissions are stored as rows in the target Sheet and migrate with the row data. The form definition itself (field order, labels, conditional logic) is documented during discovery and provided as a written spec for rebuilding in Asana Forms. Asana Forms connect directly to a Project for intake workflows, which is the functional equivalent of Spreadsheet.com's form-to-row creation model.

Spreadsheet.com automation rules (triggers, conditions, and multi-step actions) are stored server-side with no export mechanism. At migration time, there is no automation backup. We conduct an automation discovery session during scoping where the customer's admin describes each automation's trigger, condition logic, and actions. We deliver a written automation inventory with recommended Asana Rules equivalents, and the customer's admin rebuilds them post-migration in the Rules builder.

File attachments stored in Spreadsheet.com cells are extracted as binary files with their original filenames. We map them to Asana task attachments via the Asana attachments API. Files exceeding 100MB are flagged and skipped per Asana's API limit; files within the limit associate to the corresponding task by row ID. Customers whose Spreadsheet.com attachments exceeded 100MB must re-upload those files manually or use an external file storage integration.

Spreadsheet.com cell-level and sheet-level comments export as text annotations with author attribution where metadata is available. We append comment text to the relevant task record in Asana using the format '[Comment by {author}]: {text}' appended to the task description, or as a task comment if the destination supports it via API. Author attribution is preserved as text in the comment body.

Spreadsheet.com user accounts and workbook-level permission sets are not exported via any shutdown tooling. We reconstruct the permission hierarchy from any available workbook sharing metadata or CSV exports. Mapping to Asana requires provisioning workspace members manually in the destination Asana workspace, then assigning project-level roles (Member, Commenter, Viewer) based on the reconstructed Spreadsheet.com permission level. Owner-level access in Spreadsheet.com maps to Project Admin in Asana.