Migrate from CINC to Twenty CRM

CINC Lead records map directly to Twenty People. FlitStack preserves the CINC lead status as a custom select field (CINC_Lead_Status__c) on the Twenty People record to maintain report continuity across the migration. Leads without a company association land as standalone People records. Original created dates and agent assignments are preserved as custom datetime and text fields for historical reference.

CINC Contact records map to Twenty People. The mapping preserves CINC's contact status (active/inactive) as a custom field. If a CINC Contact is linked to a Company, the companyId is resolved to a Twenty Companies record and linked via the People.company field.

CINC distinguishes between Leads and Contacts by status. FlitStack splits on CINC's lead_status field: 'New Lead' and 'Contacted' route to Twenty People with a custom lead_source field; 'Active' contacts land as Twenty People with a customer flag. Status history is preserved in a custom text field for audit.

CINC Company records map 1:1 to Twenty Companies. Parent-company hierarchies in CINC map to Twenty's parentCompany relation field. Multi-contact companies are fully preserved — all linked People records reference the same Twenty Company, maintaining the organizational structure from CINC in the migrated data.

CINC Deal records map to Twenty Opportunities with field-by-field translation. Deal name maps to Opportunity.name, amount maps to amount, close_date maps to closeDate, and owner maps to the Opportunity.accountManager field. CINC pipeline stage names are mapped to Twenty Opportunity stage values to preserve deal tracking continuity.

CINC Pipelines (which define the stages a Deal moves through) map to Twenty's Opportunity stage configuration. Each CINC pipeline requires a corresponding Twenty stage set. FlitStack maps CINC stage names value-by-value to Twenty stage names, preserving probability and forecast-category mapping if present in CINC.

CINC Tasks map to Twenty Tasks with full attribute preservation. Task title, description, due date, assignee, and completion status transfer directly. Linked contacts, companies, or deals in CINC are resolved to Twenty record IDs and linked via Twenty's Task relation fields, maintaining the full task context.

CINC's auto-tracked emails, calls, and texts logged via behavioral messaging are exported as CINC Tasks and mapped to Twenty Tasks with Type='Email' or Type='Call'. Original CINC engagement timestamps are preserved in the Twenty Task's dueDate or custom datetime fields to maintain the complete activity timeline.

CINC file attachments on Leads, Contacts, Companies, and Deals are re-uploaded to Twenty. FlitStack downloads each attachment from CINC (respecting file size limits) and attaches it to the corresponding Twenty record. File name and original upload date are preserved as metadata.

CINC custom fields on Leads, Contacts, Companies, and Deals become Twenty custom fields. FlitStack creates each custom field in Twenty via Settings → Data Model before the import run. Field type mapping: CINC text → Twenty text, CINC number → Twenty number, CINC picklist → Twenty select.

CINC agent assignments on Leads and Deals map to Twenty Workspace Members. FlitStack resolves CINC agent email addresses against Twenty user accounts (invited via Settings → Members). Unresolved agents are flagged before migration — their records are assigned to a fallback Twenty user.

CINC MLS listing data (listing ID, status, price, address) attached to Leads or Deals has no native equivalent in Twenty. FlitStack preserves this as custom fields on the relevant Twenty record or as a custom object if the MLS schema is complex. Rebuilding MLS sync in Twenty requires a separate integration.

CINC behavioral messaging rules (auto-triggers based on lead behavior) cannot be migrated to Twenty. FlitStack exports each rule's configuration as a reference document for your Twenty admin to rebuild in Twenty's workflow builder. No rule logic transfers automatically — manual recreation is required for each automation.

CINC auto-reassignment rules (Switchboard, Sarah, auto-reassign features) have no equivalent in Twenty's native functionality. FlitStack documents the rule conditions so your Twenty admin can build equivalent routing logic using Twenty's workflow conditions and assignees. Each rule must be recreated manually in Twenty's workflow builder.

CINC's Accounting Module (Accounts Receivable, Collections, TresRE integrations) is outside Twenty's CRM scope. These records are exported as-is for separate processing — CINC's accounting data does not map to Twenty objects and is flagged as out-of-scope in the migration plan for your finance team to handle independently.