Migrate from Stackby to Asana

Stackby's Organization (top-level container) maps directly to an Asana Workspace. The Organization name and domain settings transfer as the Workspace name and settings. User accounts and permissions assigned at the Organization level in Stackby map to Workspace membership in Asana, with roles reconciled during the discovery phase. If the customer operates multiple Asana Workspaces, we scope the migration to the target Workspace specified during discovery.

A Stackby Stack is the organizational unit containing one or more Tables. It maps to an Asana Project, which serves as the container for Tasks. Stack-level settings (visibility, sharing) require manual configuration in Asana because Project-level visibility settings differ from Stack sharing rules. We recommend the customer review Asana's project privacy settings (public to workspace, private, or shared) against the original Stack sharing configuration during discovery.

A Stackby Table within a Stack maps to an Asana Section within the corresponding Project. If the Stackby Table contains more than 500 Rows and the customer wants separate task groupings, we can split one Table into multiple Asana Projects (each becoming a separate project with its own Sections). Column definitions from the Stackby Table schema are translated to Asana custom fields on the Project; the Section name reflects the original Table name. Lookup columns referencing other Tables generate a text or ID custom field in Asana (no native cross-project lookup in Asana); the customer's admin may implement a third-party lookup solution post-migration.

Each Stackby Row maps to an Asana Task within the corresponding Section. The Row's primary text fields (Name, Description) map to Task Name and Task Description (rich text). Column values map to custom field values on the Task. Row timestamps (Created At, Updated At) transfer as custom fields or task creation metadata; Asana does not support custom created-at timestamps, so the original timestamp is stored in a custom field for audit purposes. Completed-row status in Stackby maps to Task completion in Asana.

Stackby Text and Long Text columns map to Asana Text custom fields. Character limits in Stackby columns are not enforced in Asana; we note any character limits in the field notes so the customer's admin can add validation if needed. Rich text formatting in Stackby Long Text columns (if used) is preserved as HTML in the task description but may require manual reformatting after migration.

Stackby Number and Currency columns map to Asana Number custom fields. Currency columns retain the numeric value; currency symbol and formatting do not transfer and must be reconfigured in Asana's field settings. Decimal place settings from Stackby are noted for the customer's admin to set in Asana.

Stackby Date columns map to Asana Due Date or Start Date custom fields depending on the column's semantic role (deadline vs start). DateTime columns with time-of-day precision map to a custom field in Asana since Asana's native Due Date does not store time. Time zone handling is documented during discovery; UTC normalization may be required if the source and destination time zones differ.

Stackby Select columns map to Asana Enum custom fields (drop-down). The picklist values transfer as the enum options. We validate that enum option names do not exceed Asana's 255-character limit. Option color coding from Stackby is not preserved in Asana (Asana supports limited color customization per enum value but not at the level of Stackby's color picker).

Stackby Multi-select columns map to Asana Multi-select Enum custom fields. Multiple selected values transfer as multiple entries in the Asana multi-select field. Asana supports multi-select from the Premium tier onward; if the destination Workspace is on Asana Basic, we flag this as a tier upgrade requirement during discovery.

Stackby attachment columns map to Asana task attachments. Files are downloaded from Stackby via API and uploaded to Asana via the Asana Attachments API. Asana enforces a 100MB per-file limit for API-attached files; files exceeding this threshold are flagged and either skipped (with a written list for manual re-upload to Google Drive or Dropbox and link-sharing) or handled via Asana's external link attachment type. We audit total attachment volume during discovery to scope this phase.

Formula columns in Stackby (cross-column calculations, aggregations, conditional logic) are computed dynamically and cannot be expressed as live formulas in Asana. During migration, formula columns transfer as their computed value at migration time, stored as a Number or Text custom field in Asana. We flag every formula column during discovery with its original formula expression so the customer's admin can manually rebuild logic in Asana Rules (if computational) or external tools (if complex). The static value note is critical — the field will not update if source data changes after migration.

Stackby Link or URL columns map to Asana Text custom fields storing the URL string. Asana's native External Link field type is limited to specific integrations; we use Text for broad compatibility. Hyperlink formatting from Stackby is preserved as a raw URL string.

Stackby Checkbox columns map to Asana Checkbox custom fields. Boolean true/false transfers directly. Asana supports checkbox custom fields from Premium onward; we verify destination tier during discovery.

Stackby Kanban views (grouped by a Select column) map to Asana's Board view on the corresponding Project. The grouping column in Stackby (e.g., Status) maps to the Board column field in Asana. We recreate the Board configuration using the same column groupings. Note that Stackby's multi-column Kanban (grouped by multiple dimensions simultaneously) cannot be replicated in Asana's single-dimension Board; we map the primary grouping and document secondary groupings in the handoff notes.

Stackby Calendar views (based on a Date column) map to Asana's Calendar view on the Project. The date field used for calendar rendering transfers as the Calendar view's date dimension. Stackby's event color-coding by column value is noted but not replicated in Asana Calendar (which supports limited color options).

Stackby Forms (for data entry) are configuration constructs that collect responses and write to linked Tables. We migrate the Form's field structure and the resulting Rows (which are already captured as Table rows) but the Form itself cannot be replicated in Asana because Asana does not have a native form builder for task creation from external respondents. We document the Form schema (field names, types, validation rules) in the handoff package so the customer can rebuild using Asana's intake forms (Business tier), Google Forms, or a third-party form tool like Typeform or Jotform with an Asana integration.