Migrate from ConSol to Twenty CRM

ConSol contact model records map directly to Twenty People objects. Each ConSol contact's email, name, phone, and job title fields map to their Twenty equivalents. Owner resolution uses email matching against Twenty workspace members. Contacts without a primary organization map to standalone People records.

ConSol organizations map to Twenty Companies. Company name, domain/website, industry, and employee count fields translate to their Twenty Company counterparts. Parent-child organization hierarchies in ConSol map using Twenty's Company → Company self-relation field. We validate that each organization's domain is properly formatted before importing into Twenty's domain field.

ConSol case tickets do not have a native equivalent in Twenty's standard object set. We create a Case custom object in Twenty and map ticket number, status, priority, description, and created date as custom fields. Original case owners map via email matching to Twenty workspace members.

ConSol case activity logs (status changes, internal notes, customer responses) map as Twenty Notes attached to the related Case record. Original timestamps and actor information are preserved in the Note body or custom fields. We parse the activity log entries and format them consistently for readability in Twenty's Notes interface.

ConSol document attachments are metadata records referencing files stored in ConSol's document management. We extract file names, URLs, and upload metadata as a Note record in Twenty. The actual file content cannot be transferred; we document the original ConSol URL for reference.

ConSol supports N:N contact-to-organization relationships. Twenty People records have a single companyId field. We migrate the most recently updated organization as the primary companyId and surface additional associations as a custom multi-select field on the People record. We also preserve a history log of all associated organizations for audit purposes.

ConSol extended contact properties created via scripting or the REST API map to Twenty custom fields on the People object. We create fields in Twenty Settings → Data Model before migration and map values by type — text to TEXT, numbers to NUMBER, dates to DATE, and pick-lists to SELECT.

ConSol organization-level custom properties follow the same pattern as contact custom fields. We create matching custom fields in Twenty's Company object before migration. Type-aware mapping applies: boolean flags, currency fields, and multi-select values each require specific field type selection. We verify all currency values use consistent decimal formatting before import.

ConSol user and owner records do not have a direct Twenty equivalent. We resolve ConSol owner IDs by matching user email addresses against Twenty workspace members. Unmatched owners are flagged for admin review and assigned to a fallback workspace member.

ConSol BPM workflows, scripts, and automated routing rules do not migrate. They must be rebuilt in Twenty's Settings → Workflows (Organization tier) or via custom code using Twenty's SDK. We export ConSol workflow definitions as a JSON reference document to guide the rebuild.

ConSol's server-side scripting objects and REST extensions are bespoke code with no equivalent in Twenty. Custom integrations that relied on ConSol scripting must be rebuilt as Twenty API clients or webhook handlers. We document all API endpoints used by ConSol scripts to ensure the replacement integration covers the same functionality.

ConSol report configurations and dashboard layouts do not transfer. The underlying data (contacts, organizations, case tickets) migrates but report definitions must be recreated as Twenty views or via a BI tool connected to Twenty's API. We provide a mapping of ConSol report metrics to Twenty field references to assist with report recreation.