Migrate from Sage CRM to Twenty CRM

Sage CRM Companies map directly to Twenty CRM Companies. We extract the CompanyID, CompanyName, Address fields, Industry, Classification, and any custom Company fields via SQL query or REST API. The CompanyName becomes the display name in Twenty; we use CompanyID as an external ID for deduplication if the same company appears in multiple contexts. Company is imported first because Contacts and Opportunities carry a PrimaryCompanyLink foreign key that must resolve at import time.

Sage CRM Contacts link to Companies via PrimaryCompanyLink. We extract all standard contact fields (name, email, phone, title, address) plus custom Contact fields and preserve the company association by resolving the Sage CRM CompanyID to the Twenty CRM Company UUID created during the Company import phase. Duplicate detection uses email as the primary dedupe key, with an optional secondary check on FirstName + LastName if the customer has duplicate-contact cleanup requirements.

Sage CRM Leads are a separate entity from Contacts with their own lifecycle stages, qualification fields (LeadSource, LeadStatus, Rating), and source tracking. Twenty CRM does not have a separate Lead object in the traditional sense — unqualified prospects are handled as Persons attached to a Company with a Lead status field. We map Sage CRM Lead records to Twenty CRM Persons, setting a lead_status custom field or using Twenty's built-in opportunity-stage tracking. The Lead's source and qualification data migrate to custom fields on the Person record.

Sage CRM Opportunities map directly to Twenty CRM Opportunities. We extract pipeline stage, revenue amount, expected close date, probability, owner assignment, and any custom Opportunity fields. Sage CRM's pipeline configuration maps to Twenty's opportunity pipeline with stage names translated to Twenty's stage model. Multi-currency amounts migrate with the currency code preserved in a custom field if Twenty's multi-currency is not enabled.

Sage CRM Cases (service/ticket object) with severity, status, assignment, and resolution fields map to Twenty CRM Tasks if the customer's service process is simple, or to a custom object (e.g., SupportCase) in Twenty if the case model includes threaded communications and SLA fields. Case-threaded communications stored in the Communication table with a CaseID reference migrate as Comment records linked to the migrated Case. We determine the target during scoping based on case complexity and SLA requirements.

Sage CRM Communication records store emails, call logs, and meeting notes linked to entity IDs (Company, Contact, Lead, Opportunity, or Case). Twenty CRM does not have a native Communication equivalent, so we map Communications to a combination of Twenty CRM Comments (on Company, Contact, or Opportunity records) and Tasks (for call logs and meeting notes with timestamps and dispositions). Email body content migrates as a Comment; call logs migrate as a Task with TaskSubtype=Call and duration preserved in a custom field. CommunicationDate becomes the ActivityDate or Comment creation timestamp.

Sage CRM Custom Entities (user-defined tables with their own fields and relationships) map to Twenty CRM Custom Objects. Each Custom Entity has an internal table name (e.g., CustomEntityname) that differs from its UI display name — we cross-reference the API model service with the UI to build an accurate entity map. Custom Entity fields migrate as Twenty custom fields on the corresponding Custom Object. Custom Entity relationships that reference Companies, Contacts, or Opportunities migrate as lookup fields in Twenty. The customer defines the Custom Object name during scoping.

Sage CRM Users with role-based security profiles map to Twenty CRM WorkspaceMembers. We extract UserID, email, name, and active status. Role assignments (SecurityProfile) are documented as a written mapping to Twenty CRM workspace roles during scoping since the permission model differs structurally. Inactive Sage CRM users migrate as inactive WorkspaceMembers to preserve historical assignment records without granting active access.

Sage CRM Reports stored in the report schema with entity field references by internal IDs do not migrate as functional reports. We export report definitions, data sources, and scheduling configuration as a written inventory. The customer recreates key reports in Twenty CRM's reporting interface or connects a BI tool (Metabase, Grafana, or a data warehouse) to the Twenty PostgreSQL database for complex reporting needs.

Sage CRM Workflow rules with ASP-scripted actions, escalation triggers, and approval chains cannot be extracted as portable configuration. We deliver a written workflow inventory documenting every active Sage CRM workflow rule with its trigger conditions, action sequence, escalation configuration, and a recommended Twenty CRM equivalent (manual process, Twenty Workflows beta feature, or a separate automation tool). The customer's admin rebuilds the highest-priority workflows post-migration.