Migrate from Socrates to Twenty CRM

Socrates contact records map directly to Twenty CRM's People object. The key difference is that Socrates embeds company as a contact property; Twenty CRM requires a companyId foreign key. We resolve each contact's primary company in Socrates and link it to the matching Twenty CRM Company record before People records are imported.

Socrates company or account records migrate to Twenty CRM's Companies object. Domain names export from Socrates and map to the domain field Twenty CRM uses for company matching during People imports. Parent-child company hierarchies in Socrates become ParentId relationships in Twenty CRM.

Socrates deal records map to Twenty CRM Opportunities. Deal name becomes Opportunity name, amount maps to amount, and close date maps to closeDate. The pipeline and stage values from Socrates require value-by-value mapping to the stage pick-list values defined in Twenty CRM's workspace.

Socrates engagement activities (calls, emails, meetings) all become Twenty CRM Tasks. We set the Type field on each Task to indicate the original activity type. Original timestamps, subjects, and owner assignments are preserved. Call disposition notes from Socrates migrate as Task body text.

Socrates notes migrate as Twenty CRM Notes. Notes attach to the parent People, Company, or Opportunity record based on the association stored in Socrates. We preserve the original note body text, author, and create timestamp. The original associations ensure notes appear in the correct context within Twenty CRM's timeline view for each linked record.

Socrates owner IDs resolve against Twenty CRM users by email match. All target users must be invited and accepted in Twenty CRM before the migration runs — this is a prerequisite FlitStack AI surfaces in the migration plan. Unmatched owners are flagged and assigned to a fallback owner before records commit.

Socrates custom properties on contacts become custom fields in Twenty CRM. We create each field in Settings → Data Model before the People import runs. Field types map based on Socrates' property type (text → text, number → number, pick-list → select, multi-select → multi-select). The migration plan includes a custom field creation checklist.

Socrates custom properties on deals map to custom fields on Twenty CRM Opportunities. As with People, we pre-create these fields in Twenty CRM's data model before the Opportunities CSV is loaded. Pick-list custom properties on deals require value-mapping to the select options defined in Twenty CRM.

If Socrates contains custom objects, they map 1:1 to Twenty CRM custom objects. Custom-object relationships that Socrates stores as N:N associations need junction objects in Twenty CRM — we surface this in the migration plan and configure the junction table during the schema setup phase.

Socrates file attachments associated with contacts, companies, or deals are re-uploaded to Twenty CRM's file storage. We preserve the original filename and attach each file to the corresponding record in Twenty CRM. Inline images embedded in notes are downloaded and rehosted as file attachments.

Socrates workflow rules, automated sequences, and trigger-based automations have no migration path to Twenty CRM. FlitStack AI exports the rule definitions as a structured JSON reference document your team uses to rebuild each automation in Twenty's workflow builder. This step happens post-migration and is scoped separately from the data migration.

Socrates reports and dashboards do not migrate directly — the underlying data arrives in Twenty CRM intact, but all report definitions and saved views must be rebuilt manually. We provide a structured reference export documenting each report's filters, grouping, and chart configurations to guide the rebuild. Twenty CRM's reporting and dashboarding capabilities are scoped separately in the migration plan.