Migrate from Efficy CRM to Twenty CRM

Efficy Companies map directly to Twenty Company records. The company name maps to Company.displayName, website to Company.domainName, and industry to a custom field we create during schema setup because Twenty does not ship an industry picklist out of the box. We create the Company records first in the migration sequence because both Contacts and any Opportunity-linkable entities reference them as the top-level parent. Efficy's multi-address support on Company maps to custom address fields or to a related custom address object we pre-create in Twenty's metadata API.

Efficy Contacts map to Twenty Person records. The mapping is straightforward for standard properties: name, email, phone, and address transfer directly. The Company linkage uses Efficy's CONTACT link to COMPANY and maps to Twenty's Person.companyId field pointing to the previously migrated Company record. Efficy custom fields on Contact require explicit mapping to Twenty custom fields on Person, which we create during the schema preparation phase. Multi-address contacts from Efficy may require flattening to a single address or a custom address object depending on usage frequency.

Efficy Opportunities map to Twenty Opportunity records. The pipeline stage name maps to Opportunity.stage, deal value to Opportunity.amount, and expected close date to Opportunity.closeDate. Owner assignment migrates via email-to-user resolution. We resolve the Company link to Opportunity.accountId using the Company mapping created in step one. Efficy's deal priority or probability maps to a custom field because Twenty does not ship a native probability percentage field on Opportunity by default.

Efficy activity records (calls, emails, meetings, tasks) linked to Contacts or Opportunities migrate to Twenty's activity timeline on the corresponding Person, Company, or Opportunity record. We preserve the parent linkage by resolving the Efficy CONTACT or OPPORTUNITY reference to the Twenty ID at migration time. Call duration, disposition, and meeting location transfer to custom fields on the activity record. Email body content migrates as an activity note. Task status and priority map directly.

Efficy's project management module with Kanban views, milestones, and resource management maps to a Twenty custom object we create via the /metadata API before migration runs. The custom object schema includes fields for project name, status, start and end dates, and any milestone flags stored in Efficy. Tasks within the project migrate as activities on the custom Project record via a custom link field. Nested task dependencies require flattening or a custom dependency field depending on the destination's capability.

Efficy ticketing module records with status, priority, and agent assignment map to a Twenty custom object for support cases. We create the Ticket custom object during schema preparation with fields for ticket ID, status, priority, agent, and customer. Conversation history from Efficy ticket threads migrates as threaded comments or activity notes on the Ticket record. Custom ticket fields from Efficy require explicit mapping to equivalent custom fields on the Twenty Ticket object.

Efficy custom fields on Companies, Contacts, Opportunities, and other objects migrate to Twenty custom fields created via the metadata API before data import begins. We extract the full field schema per object during discovery, create the equivalent Twenty custom fields with matching data types (text, number, date, picklist), and then map the field values during the data migration phase. This ensures schema exists before data, avoiding import failures on records with custom field values.

Efficy users with roles and assignments map to Twenty WorkspaceMember records. Owner assignments on Efficy Opportunities and Activities resolve to the corresponding Twenty WorkspaceMember by email match. Inactive Efficy users are excluded from user count mapping but their historical owner assignments on records are preserved in the migrated data with the assignment intact.

Documents attached to Efficy Companies, Contacts, or Opportunities migrate as file attachments on the corresponding Twenty record. We flag any documents without a download URL in Efficy's system and flag them for the customer's admin to handle manually after migration. For documents with URLs, we migrate the attachment reference and note the source URL for re-download if needed. Binary document blobs require Efficy's export capability to be confirmed before migration.

Tags on Efficy Companies, Contacts, and Opportunities map to Twenty Tag records linked via the standard tag association. Efficy segments and list memberships flatten to tags on individual records because Twenty's tag model is object-level rather than list-based. We extract all unique tag values during discovery and create them in Twenty before the record import phase.

Efficy automation rules, follow-up sequences, and workflow triggers do not export via the API or import wizard. We document every active automation during discovery with its trigger, conditions, and actions, and deliver a rebuild specification in a written inventory document. The customer uses this document to recreate logic in their chosen automation layer (webhooks, third-party tools, or custom code). Rebuild effort is estimated separately and is not included in standard migration scope.