Migrate from Cirrus CRM to Twenty CRM

Cirrus CRM Company records map directly to Twenty CRM Company. The credit information fields and geographic enrichment (latitude/longitude) stored in Cirrus CRM migrate as custom fields on the Twenty CRM Company record. Company is the first object imported because Contacts and Deals depend on a resolved CompanyId. We validate that all required Company fields (name, domain) are populated before import and flag duplicates based on domain match for the customer's admin to resolve.

Cirrus CRM Contact records map to Twenty CRM Person objects. Standard fields (name, email, phone, address) migrate directly. The Contact-to-Company relationship migrates as a PersonCompanyRelation record in Twenty CRM, preserving the original association. Custom fields on Contact are mapped field-by-field after the customer confirms the Cirrus CRM tenant schema configuration during scoping.

Cirrus CRM Deals map to Twenty CRM Opportunity records. The monetary value, close date, and stage label migrate as-is. Note that Cirrus CRM pipeline definitions (stage order, automation triggers, win/loss criteria) are not stored on the Deal record; we treat stage labels as static text fields unless the customer explicitly requests pipeline configuration migration. We flag any Deals with stage labels that do not match an existing Twenty Opportunity stage for manual mapping before import.

Cirrus CRM pipeline configurations require manual recreation in Twenty CRM because pipeline definitions are stored in the platform schema, not in the Deal record. We deliver a written map of every Cirrus CRM pipeline with its stage names, stage order, and probability percentages. The customer's admin creates the corresponding Opportunity pipeline and stages in Twenty CRM Settings before the Deal import phase. This step gates the Deal migration; we cannot import Deals without a resolved pipeline.

Cirrus CRM Quotes carry line items and product associations and are referenced by Order records. Twenty CRM does not have a native Quote object as standard, so we create a Custom Object named Quote with fields for quote number, total amount, status, and line item JSON. The Quote-to-Deal relationship is preserved by storing the parent Opportunity ID on the Quote record. The customer confirms during scoping whether quotes should be migrated as formatted objects or simplified Opportunity-level records.

Cirrus CRM Orders are generated from Quotes and linked to ERP records. We create a Custom Object named Order with fields for order number, order date, total amount, and status. The Order-to-Quote relationship and the Order-to-ERP-reference are stored as custom fields on the Order record. Order-to-invoice relationships are migration-critical for teams planning to continue ERP sync; we preserve the ERP invoice reference in a custom field for the customer's admin to reconnect in their middleware layer post-migration.

Cirrus CRM Activities log calls, emails, meetings, and tasks tied to Contact or Deal records. We migrate the activity record and its timestamp; the activity display format (timeline view vs. list) differs between platforms. Calls and meetings migrate as Task records with a custom type field; emails migrate as Note records attached to the Person or Opportunity; standalone tasks migrate as Task records. We preserve the activity timestamp and the associated Person or Opportunity ID for timeline integrity.

Cirrus CRM Campaigns track objectives and campaign-level metrics. Twenty CRM does not have a native Campaign object as standard. We create a Custom Object named Campaign with fields for campaign name, status, start date, end date, and budget. Individual campaign member associations (which Contacts are in which Campaigns) are stored as CampaignMember records linking Person to Campaign. The customer confirms the scope of campaign member migration during scoping because large campaign histories can extend migration time.

Cirrus CRM custom fields require field-by-field mapping because Cirrus CRM tenant schemas are not universally exported. We ask the customer to provide a screenshot or export of their Cirrus CRM field configuration before migration, then validate field types (text, number, date, picklist) in a test batch of 50 records before committing to the full dataset. Custom fields are created in Twenty CRM Settings before the parent record import. Type mismatches (text vs. number, date format) are resolved in the transform layer before import.

Cirrus CRM User records map to Twenty CRM WorkspaceMember. We resolve owners by email match across both platforms. Any Cirrus CRM User without a matching Twenty CRM WorkspaceMember is held in a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId is required on Opportunity records; migration cannot proceed past Opportunity import until all referenced owners are provisioned.

Cirrus CRM attachments are exported as individual files named by record and file type. A Contact with three attachments produces three files. We batch-associate these to the correct Twenty CRM Person, Company, or Opportunity record by filename parsing and provide a manifest mapping each file to its target record. Files exceeding 10 MB are flagged for manual handling. The customer confirms whether attachments should be stored in Twenty's file storage or in an external S3-compatible bucket.