Migrate from OnePageCRM to monday CRM

OnePageCRM Contact records map to Monday CRM People items on the CRM People board. We map standard fields (name, email, phone, address, social URLs) to their corresponding Monday column types. Custom contact fields map to Monday columns of equivalent type (text, number, date, dropdown). Next Action date from OnePageCRM maps to a custom date column NA_next_action_date__c. We deduplicate by email address on import and flag any contacts with duplicate emails for manual reconciliation.

OnePageCRM Organization records map to Monday.com People items with a company_name column filled in, or optionally to a dedicated Organizations board if the customer uses Monday's multi-entity linking. We preserve the contact-to-organization linkage by storing the organization reference as a text column or linking items via Monday's relation column. Company-level custom fields map to Monday columns with equivalent types.

OnePageCRM Deals map to Monday CRM deal items on the Deals board. Deal name, amount, pipeline stage, close date, margin, commission, and cost map to corresponding Monday columns. The deal's associated Contact maps to a Person or link column pointing to the CRM People board item. We configure the Deals board's Group By setting to mirror OnePageCRM's pipeline stages using Monday's Status column.

OnePageCRM Status values (Prospect, Qualified, Customer, etc.) map to Monday Status column options on the Deals board. We create a Status column with options that match the source taxonomy, preserving the ordering for Kanban view grouping. Closed-Won and Closed-Lost statuses from OnePageCRM carry over as terminal Status options with color coding.

OnePageCRM custom fields must be pre-created in the destination board as columns before migration. We provide a custom field checklist during scoping so that all source custom fields have a Monday column equivalent created in advance. Unsupported column types (e.g., OnePageCRM multi-select tags exceeding Monday's dropdown length) are flagged and mapped to text columns with pipe-delimited values as a fallback.

OnePageCRM tags assigned to Contacts carry through as Monday Tags or Labels column values. Tags are stored as a flat namespace and imported as-is. If the customer uses tags for segmentation, we recommend using Monday's Tags column for filtering and reporting. Tags do not merge or de-duplicate across records; we carry the full source tag set.

OnePageCRM Lead Source values (website inquiry, phone call, referral, etc.) map to a Monday Dropdown column on the CRM People board. Pre-populated values migrate as dropdown options; we create any missing options before import so that the Lead Source maps cleanly without manual post-import correction.

OnePageCRM notes and call logs attached to Contacts migrate as Updates on the corresponding People item or as Subitems on the related Deal item. Call duration and disposition data migrate as text columns on the Subitem. Email body content is not available from OnePageCRM's export; we carry available metadata (addresses, dates) and document which records have missing content.

OnePageCRM Predefined Items representing products or services map to a Monday Products board or to the Price column on Deals items. We preserve item name, price, quantity, and grouping. Grouping maps to Monday Group labels or a Tags column. Products used in multiple Deals need a separate Products board with relation columns pointing to Deals items.

OnePageCRM owners assigned to Contacts, Organizations, and Deals map to Monday Person columns. We resolve owners by email match. Any owner without a matching Monday user account goes to a reconciliation queue; the customer provisions the missing user before record import resumes. Owner assignment on Deals migrates as an Assignee column with the matched user.