Migrate from Efficy CRM to monday CRM

Efficy Companies map to Companies in Monday.com CRM boards. We extract Company records via Efficy's JSON-RPC API using the searcha endpoint, preserving Company name, address fields, website, industry, and custom fields. Company is migrated first because Contacts in Efficy link to Companies via a foreign key (KVAIDNUMNOREL); Monday.com requires the parent Company item to exist before linking People items to it. We resolve KVAIDNUMNOREL to the Monday.com item ID during the import phase.

Efficy Contacts map to People items in Monday.com CRM. Standard properties (name, email, phone, address) migrate directly. The Company linkage (KVAIDNUMNOREL) resolves to the Monday.com Company item ID established during the Company import phase. Multi-address support in Efficy maps to the primary address fields on the Person item, with secondary addresses stored as custom text fields. Custom Contact fields (picklist, date, numeric, text) map to Monday.com custom columns with equivalent types.

Efficy Opportunities map to Deals in Monday.com CRM. The dealstage property maps to the Deal's Status column, with stage names preserved as Monday.com column labels. Deal value, expected close date (DATCLOTNUMNOREL), owner assignment, and custom opportunity fields migrate to the Deal item. We validate stage values against Monday.com's allowed status options before import and flag any Efficy stages that have no Monday.com equivalent.

Efficy Activities linked to Contacts or Opportunities are migrated as item updates or notes on the corresponding Monday.com Person or Deal item. Call duration, email subject and body, meeting attendees, and task status map to custom columns or as activity note entries on the item. Monday.com does not have a native Activity object equivalent to Efficy's activity log, so we use item updates and notes to reconstruct the engagement history. Activity ordering is preserved using the original Efficy timestamp.

Efficy's project management module (Kanban views, milestones, resource management) has no direct Monday.com CRM equivalent. We migrate Projects as a separate Work Management board in Monday.com, with project milestones as group items and tasks as sub-items. Nested task dependencies and resource assignments map to Monday.com sub-item columns. Customers should confirm whether Projects are in-scope during scoping, as reconstruction as a functional board requires configuration decisions that are outside the data migration per se.

Efficy Tickets (customer service records with status, priority, agent assignment, and conversation history) migrate to a dedicated Cases board in Monday.com. Ticket status maps to board column values; priority maps to a priority column; agent assignment maps to an assignee column. Conversation history migrates as item updates or as a linked note block. Custom ticket fields require explicit column creation before import. Customers using Efficy's service module for active case management should designate this board as in-scope during scoping.

Efficy custom fields on Companies, Contacts, Opportunities, Projects, and Tickets map to Monday.com custom columns. We extract the full field schema per object during discovery to build a mapping table. Field types are matched: Efficy picklist maps to Monday.com Dropdown or Tags column, date fields map to Date column, numeric fields map to Number column, and text fields map to Text column. Custom field naming conventions in Efficy may require disambiguation during mapping if multiple fields share similar labels.

Efficy Users with roles and record assignments map to Monday.com CRM users by email match. We extract all distinct owners referenced on Contact, Opportunity, Project, and Ticket records and reconcile them against the Monday.com user table. Any Efficy user without a matching Monday.com user goes to a reconciliation queue for the customer's admin to provision before record import resumes. Historical assignments on closed Deals or past Activities are preserved as assignee values even if the original user is no longer active.

Efficy automation rules and follow-up sequences are not exportable via the JSON-RPC API or any export tool. They do not migrate to Monday.com's automation builder because the trigger conditions, actions, and delay logic differ structurally. We document every active Efficy automation during discovery, noting its trigger, conditions, actions, and recommended Monday.com automation equivalent. The customer's admin rebuilds automations in Monday.com's automation builder using this inventory as a guide. This is outside the data migration scope.

Documents attached to Efficy Companies, Contacts, or Opportunities are migrated as file attachments on the corresponding Monday.com item where a download URL is available. We flag any document without a valid URL as requiring manual re-upload by the customer post-migration. Monday.com stores file attachments as item-level files linked to the parent item. Document metadata (file name, upload date, attached-by user) is preserved where available from Efficy's API.