Migrate from Unanet CRM by Cosential to Twenty CRM

Unanet Contact maps directly to Twenty People. Every standard contact field (name, email, phone, job title, address) maps to its Twenty People equivalent. Contacts associated with multiple Unanet companies require a primary company assignment with secondary associations preserved in a custom field.

Unanet Company maps to Twenty Company. Company name, domain/website, industry, employee count, and revenue transfer as direct field mappings. Unanet company hierarchies (parent/child) map to the Twenty Company parent field. Multi-company contact associations collapse to one primary companyId with secondary companies stored in a custom relationship field.

Unanet Deal maps to Twenty Opportunity. Deal name, amount, and expected close date transfer directly. Pipeline stages from Unanet map to Twenty Opportunity stage values — each Unanet pipeline stage name requires explicit value mapping to a Twenty stage option (or a custom stage pick-list if the pipeline has more than 5 stages).

Unanet activity records (call logs, emails, meetings, tasks) map to Twenty Tasks with Type differentiation. Email subject lines and body text migrate to the Task subject or a linked Note. Original activity timestamps and owners are preserved on the Twenty record. Unanet's Outlook-synced emails that were stored as activity records export as Tasks with the email subject as the Task name.

Unanet's personnel module (tracking staff experience, certifications, and project associations) has no native equivalent in Twenty. We migrate this as a custom Personnel object in Twenty with fields for personnel type, name, contact details, and a custom field capturing the Unanet personnel ID for traceability. Personnel-to-company associations map as lookups to the Company object.

Unanet's proposal and publishing content (project profiles, qualification statements, resumes, government forms) migrates to a custom Proposal object in Twenty. Proposal content sections migrate as rich-text fields. Proposal templates migrate as read-only Note records with a custom field flagging them as template originals — they cannot be used for auto-population in Twenty and must be rebuilt in the workflow builder.

Unanet users and deal owners resolve by email match against Twenty Workspace Members. If a Unanet user does not have a corresponding Twenty account, their records are assigned to a fallback owner (or flagged for manual reassignment before migration). Active vs inactive user status in Unanet maps to the account status in Twenty.

Unanet file attachments on companies, contacts, and deals re-upload to Twenty's attachment structure. Files are linked to the parent record (People, Company, or Opportunity) by ID. Large files that exceed Twenty's storage limits are flagged for manual re-upload with the original file name and URL preserved as a reference note.

Unanet custom objects map 1:1 to Twenty custom objects when the target object already exists in the Twenty workspace. When a Unanet custom object has no corresponding Twenty object, we create one with the Unanet field schema. Custom object relationships that are N:N in Unanet require junction objects in Twenty if the association is many-to-many.

Unanet supports N:N relationships between contacts and companies natively. Twenty's People object has a single companyId lookup. We migrate the most recently modified company association as the primary companyId and store all secondary company IDs as a comma-separated custom field (Secondary_Company_Ids__c) for reference and manual reconciliation.

Unanet's project/pursuit records track project-specific data including directories, financials, logistics, and marketing documentation. These have no native Twenty equivalent. We migrate as a custom Project object with fields for project name, status, associated company, key dates, and a link to the primary opportunity. Project-specific documentation migrates as Note records attached to the Project.