Migrate from edge CRM to Twenty CRM

edge CRM Contacts map to Twenty People. The edge CRM contact's email becomes the People email field (used as dedupe key), name splits to firstName and lastName, and any phone, address, or custom field values map to their Twenty equivalents. We resolve edge CRM's company association to a Twenty Company record by domain match before Contact import so that the workspaceId relation is satisfied at insert time.

edge CRM Company records map directly to Twenty Company. The company domain becomes the Company domain field, which Twenty uses for link previews and reverse contact lookup. Company is imported first in the sequence so that People records can reference a valid Company workspaceId on insert rather than arriving as orphaned contacts without an account linkage.

edge CRM Deals map to Twenty Opportunity. The deal name becomes Opportunity name, deal amount maps to Opportunity amount, and the close date maps to Opportunity closeDate. The edge CRM deal stage maps to a Twenty Opportunity stage, which must be pre-created in Settings → Data Model with a matching stage name before Deal import begins. The deal owner maps to a Twenty User by email lookup.

edge CRM supports a separate Lead object distinct from Contacts, typically enriched with AI-scored qualification data. If the customer uses edge CRM's Lead object as a distinct stage before Contact conversion, we map Leads to Twenty's Lead object. If the customer's edge CRM uses Leads interchangeably with Contacts (common in SMB workflows), we consolidate them into Twenty People. The split rule is defined during scoping based on whether edge CRM's Lead records have distinct fields or lifecycle stages not present on Contacts.

edge CRM allows custom stage names and ordering per pipeline. We extract the full stage list including custom names, sequence order, and probability weights, then configure matching Opportunity stages in Twenty's Settings → Data Model before Deal migration. Each stage must exist in Twenty before Deals referencing that stage are imported via CSV.

edge CRM Activities (calls, emails, meetings, notes) map to Twenty Task or Note records. Calls and tasks become Task with the activity type stored as a custom field. Meeting metadata (date, duration, attendees) stores in Task fields or as a Note with the meeting summary body. Emails become Note records with the email body and metadata. Each activity inherits the link to the related People, Company, or Opportunity record via Twenty's workspaceId and activityTargetIds.

edge CRM follow-up Tasks map directly to Twenty Task. Completed and open tasks both transfer. Due date maps to dueAt, completion status maps to Task status (completed/open/overdue), and task body migrates as the Task description. Assignee resolves by email match to a Twenty User record.

edge CRM allows teams to define custom properties on Contacts, Companies, Deals, and Leads. We extract the full custom field schema from edge CRM, map field types to their closest Twenty equivalent (text, number, date, select, multiselect), and pre-create each field in Twenty Settings → Data Model before any CSV import runs. Twenty's CSV importer creates records, not fields — a critical difference from edge CRM's inline field creation that requires this configuration step to happen first.

edge CRM stores the relationship between Contacts and Companies as a first-class association. We extract every contact-company association and recreate it in Twenty by importing People with their domain-matched Company workspaceId. For edge CRM contacts without a company association, we either attach them to a catch-all Company or import them as unlinked People, depending on the customer's preference during scoping.

edge CRM links Deals to Contacts as opportunity stakeholders. We preserve these associations by mapping edge CRM deal-contact links to Twenty's opportunityContactRole equivalent or activityTargetIds on the Opportunity record. The association migrates after both the Opportunity and the People records are loaded so that the foreign key resolution succeeds.