Migrate from FIVE CRM to monday CRM

FIVE CRM Contacts map to Monday.com CRM People items. Email address, phone number, and owner assignment migrate via CSV import or API. We enumerate all standard and custom fields on Contact during the pre-migration field mapping session, type each field against Monday.com CRM column types (text, number, date, phone, email), and resolve owner email matches to Monday.com CRM users. Contacts without an email are flagged for manual review because Monday.com CRM relies on email as a primary identifier.

FIVE CRM separates Leads from Contacts in its data model. Monday.com CRM uses a unified People entity for both. We merge all FIVE CRM Leads into People items, preserve the original Lead_Source as a custom text column in Monday.com CRM, and set a Lead_Status column to differentiate migrated Leads from migrated Contacts. This merge happens at migration time using a source-object flag we add to every record during the transform phase.

FIVE CRM Companies map to Monday.com CRM Organizations. Organization is created before any Contact import to preserve the People-Organization linkage. The FIVE CRM company name becomes the Organization name; domain and address fields map to the equivalent Monday.com CRM Organization columns. Name-based deduplication is applied during import to prevent duplicate Organizations.

Each FIVE CRM Pipeline becomes a separate Monday.com CRM board with a Status column representing the pipeline stages. We map the stage names from FIVE CRM (which vary by tenant configuration) to Monday.com CRM Status column values during scoping, explicitly renaming any stages that conflict with Monday.com CRM's reserved values. Custom pipeline fields from FIVE CRM become custom columns on the new board.

FIVE CRM Campaigns track email marketing sequences and contact membership. Monday.com CRM does not have a native Campaign object in the same structure; we create a Campaign board in Monday.com CRM to serve as a campaign registry, and link People items to campaigns using a Link to Items column or a Tags column. Campaign status flags and contact-level engagement indicators migrate as custom columns on the People item. Per-email event logs (opens, clicks) require a separate export from FIVE CRM because the bulk export endpoint is not available, and are noted as a manual import step.

FIVE CRM Tasks with due dates, assignees, and completion status map to Monday.com CRM items. We map the task assignee to the Monday.com CRM user (resolved by email), due date to the Date column, and status to the Status column. FIVE CRM task types are consolidated into a single task item type in Monday.com CRM unless the customer requests separate board structures per task category.

FIVE CRM custom fields are enumerated during the pre-migration field mapping session. We map each custom field to the closest Monday.com CRM column type: telemarketing-specific drop-down fields map to Monday.com CRM Dropdown or Status columns; numeric scoring fields map to Number columns; text notes map to Long Text columns. FIVE CRM's opaque error messages mean we extract the full field schema directly from the export rather than relying on the UI to surface type information. Fields with inconsistent naming or types across the tenant are flagged for customer review before the mapping is finalized.

FIVE CRM Users map to Monday.com CRM Users by email match. Roles and permission levels do not transfer directly because Monday.com CRM's permission model is workspace and board scoped rather than role-based. We note each FIVE CRM user role for the customer's admin to reassign permissions post-migration in Monday.com CRM's Workspace Settings.