Migrate from Favro to Microsoft Project

Favro Cards map directly to Microsoft Project Tasks. Card title becomes Task Name. Card description migrates to the Task Notes field as plain text. Assignee maps to the Task's Resource Names field. Due date maps to either Deadline or Start/Finish depending on the Card's date model in Favro. Labels migrate to a multi-value text custom field or to the Task's Flag field for color-coding. Each Card becomes one Task record, and the full set of Cards from all Boards concatenates into a flat task list within the destination Project.

Each Favro Board maps to a Microsoft Project file (.mpp) or a Project Online project plan. Board columns (workflow stages) do not map directly — Microsoft Project uses Stage as a drop-down custom field rather than a horizontal lane. We create a BoardStage custom field on Task and populate it with the originating Board column name so the customer can filter by Board origin in the destination. Board-level permissions do not migrate; Project-level permissions are managed through SharePoint Online sharing settings or PWA security groups.

Favro Collections aggregate multiple Boards for management visibility. Microsoft Project has no native Collection equivalent, so we create Summary Tasks at the top level of the destination Project plan, with each constituent Board's tasks inserted as sub-tasks beneath the Summary Task named after the Collection. If the destination is Project Online, Collections map to separate project plans linked via a Project Site in SharePoint, and we document the linking structure in the migration inventory.

Favro Relations linking one Card to another map to Microsoft Project Predecessor links on the Task form. We resolve the Card IDs at migration time and assign FS (Finish-to-Start) as the default dependency type. Circular dependency detection is run against the full relation graph before import; any circular links are flagged for the customer's PMO to resolve manually before the project plan is finalized. Lag time from Favro Relations does not map to Microsoft Project lag fields without manual review because lag interpretation varies by project.

Favro Labels applied to Cards migrate to a multi-select text custom field on the Task or to Flag Items for color-coded tracking. We deduplicate label names during import and create the destination custom field schema before migration. If the destination is PWA (Project Web App), we use Enterprise Custom Fields configured at the Task level. Label colors do not map; the customer assigns Flag colors post-migration based on the label name inventory we deliver.

Favro custom fields on Cards (dropdown, date, number, text) require pre-creation in Microsoft Project's schema. For Project Online and Project Server, we configure Enterprise Custom Fields at the Task level via PWA Server Settings before import. For Project Desktop, we use custom Text, Number, Date, and Flag fields. Field type mapping: Favro dropdown becomes a Lookup Table custom field in PWA; Favro number becomes a Number custom field; Favro date becomes a Date custom field. Custom field values are imported as part of the task CSV or via the REST API for PWA.

Favro Card comments, including threaded replies, migrate into the Task Notes field. We concatenate comments chronologically with author attribution and timestamp prefixes so the full comment history is preserved in a single Notes field. If comments exceed the typical Notes field character limit for very active Cards, we split into primary Notes and a secondary Notes extension record referenced in the migration inventory. Threaded replies preserve their parent-child order in the concatenated output.

Favro Card attachments migrate as linked files in Microsoft Project. We extract attachment URLs from Favro's stored file references and re-attach them during migration. Files that were uploaded directly to Favro are re-downloaded and attached to the corresponding Task record. Microsoft Project attachments have a practical limit of approximately 50 attachments per project plan; for Cards with more than that, we flag the excess and recommend the customer migrate those files to SharePoint and link them by URL instead.

Favro guest accounts and external members with limited Board access require a decision during scoping: promote to full users in the destination or preserve their access restrictions as Resource-level restrictions in Project. We flag all external member records during discovery. If the destination is Project Online, external members map to Resources with the Booked As set to Material and no calendar association, or to Windows accounts with external tenant access depending on the customer's Azure AD configuration.

Favro's timesheet tracking is available only on the Enterprise plan and captures hours logged against Cards. If the destination is Project Server Subscription Edition, timesheet entries migrate as timephased task assignment data against the relevant Task. For Project Online, Project for the Web, or Project Desktop, timesheet migration is not available natively; we document the timesheet data as a separate export and the customer can load it into a SharePoint list or Power BI dataset as a supplemental reporting layer.

Favro Automations (triggers and actions) are not accessible via API in a migratable form. We document each active automation as part of migration discovery, describing the trigger, conditions, and actions in plain language with a recommended Power Automate equivalent where one exists. The customer's PMO or Power Platform admin rebuilds the automations post-migration. We do not migrate Automations as executable code.