Migrate from Favro to monday Work Management

Favro Cards migrate 1:1 as monday.com Items on the target Board. Each Card's title, description (as rich text), assignee, due date, priority, status, and creation timestamp transfer directly. Label colors and names migrate as monday.com Tags. The primary complexity is cross-board Card existence: when a Favro Card appears on multiple Boards, we create an Item on the primary Board and tag it with all relevant Board identifiers using a custom Tags column, preserving the cross-team context as a searchable attribute rather than as native multi-board membership. Custom field values on Cards map to the equivalent monday.com column type — dropdown to Status or Labels, date to Date, number to Numbers, text to Text — and any missing column types are created on the target Board before import.

Favro Boards migrate as monday.com Boards with their configured column structure, group names, and Card ordering preserved. We extract the column configuration from Favro (Kanban, sheet, or timeline view) and create matching Boards in monday.com before any Item import begins. Board-level permissions on Favro map to monday.com Workspace and Board permission settings. If the Favro Board is in a Collection, the Collection membership is noted for reconstruction in the Folder/workspace mapping phase.

Favro Collections aggregate multiple Boards on a single screen for management-level visibility. Monday.com has no direct Collection equivalent; we handle this by creating a monday.com Folder for each Favro Collection and moving the migrated Boards into that Folder. The customer can open the Folder to see an aggregated view of its constituent Boards, which approximates the Collection experience. Collection-level ordering and any Collection-specific views are documented in the deliverable as a configuration note for the customer's admin to implement manually in monday.com.

Favro Relations link Cards and Boards across teams to model dependencies or cross-functional ownership. Monday.com has two mechanisms: item links (which connect two Items and display a linked card preview) and Mirror columns (which display values from a linked Item). We map Favro Relations to monday.com item links during migration. For Relations where the linked Cards reside on different Boards, we use item links; for same-Board Relations we use Mirror columns if the customer prefers a formula-style reference. The Relation type label from Favro is preserved as a tag on the monday.com link.

Favro Labels (applied to Cards for categorization) migrate as monday.com Tags. We preserve label colors and names, deduplicate any label collisions during import, and map the label set to the target Board's Tags column. Tags are workspace-level in monday.com, meaning the same tag vocabulary is available across all Boards in the Workspace, which provides broader searchability than Favro's Board-scoped labels.

Favro custom fields on Cards (available on Standard and Enterprise) map to monday.com column types. We map each custom field by type: dropdown to Status or Labels column, date to Date column, number to Numbers column, text to Text column, person to Person column, and checkbox to Checkbox column. Boolean fields on Favro map to Checkbox or Toggle column in monday.com. We create all required columns on the target Board before Item import begins, and we flag any Favro custom field type that lacks a direct monday.com equivalent (such as formula or multi-person fields) for the customer to resolve during configuration.

Favro Comments on Cards migrate as monday.com Updates on the corresponding Item. We preserve the comment author, timestamp, and rich text content in chronological order. Threaded replies in Favro flatten into a single Update thread in monday.com, which is the standard behavior for monday.com's activity feed. @mentions in Favro comments are preserved as text references; the tagged user is not migrated as a linked mention in monday.com because monday.com's Update mentions work differently.

Favro file attachments on Cards migrate as Files attached to the monday.com Item. We handle URL-based attachments (links to external resources stored in Favro) and file uploads differently: URL attachments migrate as link columns or text fields; uploaded files are either re-uploaded to monday.com's file storage or, if the source URL remains valid, attached as an external link. We flag any attachment over 500 MB for the customer to handle separately because monday.com's storage limits vary by plan tier.

Favro guest accounts with restricted Board visibility migrate as monday.com Guests invited to specific Workspaces or Boards. We flag all external member records during scoping so the customer decides whether to promote them to full Workspace members or maintain guest-level access in monday.com. Guest access in monday.com is controlled at the Board level, which gives the customer finer-grained control than Favro's guest account model.

Favro timesheet entries (available on Enterprise only) map to monday.com's built-in Time Tracking column on Items. We preserve hours logged, date, and user attribution against the relevant Card/Item. Note that monday.com's Time Tracking is available on Pro and Enterprise plans; if the customer is migrating to a Standard monday.com plan, time tracking data is preserved as a Numbers column with a manual format note, and the customer should upgrade to Pro for native time tracking.

Favro Automations are not accessible via API in a form that allows replay in monday.com. We document every active Automation rule during migration scoping — its trigger, conditions, and actions — and deliver a plain-language automation inventory. The customer's team uses this document to rebuild equivalent rules in monday.com's automation recipe builder. We do not migrate automations as code. The automation inventory is delivered before the production cutover date so rebuilding can begin in parallel with migration preparation.

Favro Enterprise dashboards with widget configurations migrate as a dashboard export record documenting the widget types, data sources, and layout. The monday.com dashboard engine is structurally different, and we do not recreate widget configurations programmatically. The customer's admin uses the export record to configure equivalent widgets in monday.com's Dashboard view. We flag any dashboard metric that requires a data model not present in the migrated data (for example, a metric that depended on a Relation that cannot be fully replicated in monday.com).