Migrate from Favro to Asana

Favro Cards map 1:1 to Asana Tasks as the atomic work unit. Each Task receives title, description (migrated as rich text), assignee, due date, start date, and priority from the corresponding Card. Card-level labels migrate as Asana Tags. We preserve the original Card creation timestamp as a custom field favro_created_at__c because Asana's native created_at on Tasks is set at import time. Cards with no assignee migrate as unassigned Tasks in the target Project.

Favro Boards map 1:1 to Asana Projects. Board columns (Kanban swimlanes, status lanes) migrate as Asana Sections within the Project. Board-level permission settings are documented as a project-access inventory for the customer to reapply in Asana's sharing settings. Board card ordering is preserved as Section order and task position within Section.

Favro Cards that exist on multiple Boards simultaneously require resolution. We create a primary Task in the first target Project, then add Asana Task Links (or cross-project dependencies) to associate the same work item with the additional Projects. Each linked Task carries a custom field favro_also_on_boards__c listing the additional Board names, preserving the multi-team context that is core to how Favro structures cross-functional work. The customer chooses between linked records or dependency chains during scoping.

Favro Collections aggregate multiple Boards for team or management visibility. We map Collections to Asana Portfolios (Business plan) or to a tagged grouping of Projects (Basic plan) depending on the destination Asana edition. The mapping choice is made during scoping: Portfolios provide a native management view with progress reporting; tagged groupings require the customer to apply a Portfolio-like structure manually. Collection membership (which Boards belong to which Collection) is preserved as Portfolio membership or as a custom tag applied to each Project.

Favro Relations link Cards and Boards across teams to model dependencies or cross-functional ownership. We map Relations to Asana Dependencies (blocker-blocked pairs) for dependency-type Relations, and to Task Links (relates-to) for association-type Relations. The Relation type is documented during scoping and the appropriate Asana link type is selected per Relation instance. Cross-board Relations are resolved against the split-card mapping so that the correct Task instances are linked in the destination.

Favro Card custom fields (dropdown, date, number, text) map field-by-field to Asana Custom Fields of matching type. Multi-select dropdown fields in Favro map to Asana multi-select custom fields. We pre-create all custom fields in the destination Asana Project via the API before Task import begins. If a Favro custom field name conflicts with an existing Asana custom field in the same Project, we append a numeric suffix per Asana's custom field naming convention.

Favro Labels applied to Cards migrate as Asana Tags. Label colors are preserved as hex values in a custom field tag_color__c on the Tag because Asana Tags do not natively support color metadata. We deduplicate any label collisions during import where the same label name exists in multiple Boards.

Favro Comments on Cards migrate as Asana Comments on the corresponding Task. Author attribution is preserved by matching the comment author's Favro user ID to the migrated Asana User (resolved by email). Comment timestamps are preserved. Threaded replies in Favro are migrated as a flat chronological comment list in Asana because Asana Comments do not support nested threading.

Favro file attachments on Cards migrate as Asana Attachments on the corresponding Task. We transfer file URLs from Favro's stored attachment references and re-upload to Asana's attachment storage. Attachments exceeding 100 MB are flagged in the scoping report because Asana's API does not support attachments larger than 100 MB. External URL attachments migrate as a link attachment in Asana.

Favro guest accounts with restricted Board and Collection visibility are mapped to Asana Guest membership. We flag all external member records during scoping so the customer can decide which should become Asana Guests (limited access) versus full Members. Favro guest visibility restrictions that cannot be expressed in Asana's guest model are documented as an access-inventory item for the customer's admin to reapply manually in Asana's project sharing settings.

Favro Automations are not accessible via API in a form that allows replay in Asana. We document every active Automation as part of migration scoping: trigger type, conditions, actions, and delay settings. This automation inventory is delivered as a plain-language checklist that maps each Favro Automation to a recommended Asana Rule equivalent. The customer's admin rebuilds the rules in Asana's Rule builder post-migration.

Favro Dashboards aggregate Board and Card metrics into widget-based views. We export the dashboard widget configuration as a data record but do not rebuild dashboards in Asana because the widget engine differs significantly. The dashboard inventory — widget types, Board references, metric definitions, and refresh settings — is delivered as a written handoff document so the customer's team can recreate the reporting views in Asana Portfolios, the reporting dashboard, or a connected BI tool.

Favro timesheet entries (available on Enterprise plan) migrate as time entries against the corresponding Asana Task. Asana's native time tracking is available as an add-on on Business and Enterprise plans. We preserve hours logged, date, user attribution, and any timesheet notes as a custom field group on the Task. If the destination Asana plan does not include the time tracking add-on, the data is migrated as a structured custom field set and the customer can enable the add-on post-migration.