Migrate from Corteza CRM to Twenty CRM

Corteza Leads are a first-class module with standard fields (first name, last name, email, phone, rating) and a conversion workflow that creates Accounts, Contacts, and Opportunities. Twenty does not have a separate Lead object; all individual person records are Person objects. We migrate Corteza Lead records as Twenty Person records, and we flag the lead-conversion workflow as requiring a rebuild in Twenty's workflow builder. The original conversion status (converted vs not-yet-converted) is preserved in a custom field on the Person record for audit.

Corteza Account records (representing companies) map directly to Twenty Company records. The account domain or website becomes the Company domainName field. Industry classification, address data, and social media URLs map to their equivalent Twenty Company fields. Company is the parent entity for Person in Twenty's data model, so we create all Company records before any Person import to satisfy the lookup relationship at insert time.

Corteza Contact records (individual people linked to Accounts) map to Twenty Person records. The contact-Account relation maps to the Person.companyId foreign key pointing to the migrated Company. First name, last name, email, phone, and job title migrate directly. Any custom fields on the Corteza Contact module migrate as custom fields on the Twenty Person object created via the /metadata API before import.

Corteza Opportunities track sales deals with stage, amount, probability, and close date. Each Opportunity relates to an Account and multiple Contacts via OpportunityContactRole records. We map Opportunity to Twenty's Opportunity with stage, amount, probability, and closeDate preserved. The OpportunityAccountId maps from the Corteza Opportunity-Account relation. We create Opportunity records after Company and Person records are in place to satisfy lookups.

Corteza Campaigns group marketing activities and track campaign member responses. CampaignMember records link Contacts and Leads to a Campaign. Twenty does not have a native Campaign object in its standard schema, so we create a Campaign custom object via the /metadata API with fields for campaign name, status, type, start date, and end date. CampaignMember relations migrate as a separate custom association object linking the Person (or Company) custom object to the Campaign custom object.

Corteza Cases track customer support issues with status, priority, origin, and resolution fields. Cases link to Accounts and Contacts. Twenty does not have a native Case object; we create a Case custom object via the /metadata API with the relevant fields and create a CaseContact association to the Person object. Status values migrate as a picklist on the custom object.

Corteza Contracts store agreement details with line items (ContractLineItem), related Accounts, and Contact roles (ContractContactRole). Twenty does not have a native Contract object. We create a Contract custom object via the /metadata API with fields for contract name, account (linked to Company), start date, end date, status, and terms. Contract line items migrate as a related custom object with a lookup to the parent Contract record.

Corteza Tasks can be standalone or related to any parent record (Lead, Account, Contact, Opportunity) and have status, due date, assignee, and optional description. We map tasks to Twenty Activity records with the appropriate type discriminator. Task assignees resolve by email match against the Twenty User table. Any Corteza task without a matching User goes to a reconciliation queue for the customer's admin to provision.

Corteza Events represent calendar items (meetings, calls) related to any CRM record. Each Event stores datetime, duration, organizer, and attendee references. We map Events to Twenty Activity records with the event type discriminator set. Start datetime, end datetime, and location migrate as custom fields on the Activity. Attendee references resolve by email match against migrated Person records and create ActivityParticipant records in Twenty.

Corteza's low-code environment lets administrators create entirely custom modules beyond the standard CRM set. These custom modules may have non-standard field types, custom validation rules, or non-standard relationships. We audit each custom module during discovery, pre-create the destination custom object in Twenty via the /metadata API (creating DataSource, Object, and Field metadata entries), and then migrate records via the /graphql endpoint. Custom module naming conventions are preserved as the custom object name with API-compliant naming applied.

Corteza file fields store attachments per module. The export path handles individual file records, but bulk attachment export with folder structure intact may require supplemental handling. Twenty's CSV export path explicitly excludes file attachments. We handle file migration by exporting files from Corteza's storage, uploading them to Twenty's storage layer, and creating Attachment records linked to the parent object by ID resolution. This requires supplemental API handling beyond the standard record migration sequence.