Migrate from Tubular CRM to Twenty CRM

Tubular's Contact object combines person attributes (name, email, phone, job title) and company association into a single record. Twenty separates these into Person and Company standard objects. We resolve every Tubular Contact by first checking the linked company field, creating a Company record in Twenty if one does not exist, then creating a Person record linked to that Company via the companyLink.definiteV1 field. Person.email, Person.phone, Person.jobTitle, and Person.city map directly from Tubular Contact fields.

Tubular does not have a standalone Company object; company information lives as a field on Contact. We extract distinct company names from Tubular Contact.company, deduplicate them, and create Twenty Company records. The Tubular Contact.company domain becomes the Company.website field where available. All unique company values extracted from Contacts are created as Twenty Company records before Person records are linked.

Tubular Deals map directly to Twenty Opportunities. Deal.name becomes Opportunity.name, Deal.value becomes Opportunity.amount, and Deal.stage becomes Opportunity.stageName. Deal.expectedClose and payment terms map to Opportunity.closeDate and a custom Opportunity field. Deal owner maps to Opportunity.accountOwner with owner resolution by email against the Twenty User table.

Tubular allows custom pipeline stages per deal. We map stage names and order to Twenty Opportunity.stageName values, and configure the stage order in Twenty's pipeline settings before migration. Stage probability percentages stored in Tubular migrate as a custom Opportunity.probability field if the customer requires them; Twenty's default probability auto-calculation is used otherwise.

Tubular's Lead object (distinct from Contact) contains source, status, owner, and custom Lead Builder fields. We migrate Lead records to Twenty Person records with a custom Person.isLead__c boolean set to true to preserve lead context post-migration. Lead status and source are stored in custom Person fields leadStatus__c and leadSource__c. Lead conversion in Twenty requires the admin to create a Company record and link the Person, which we document as a post-migration step.

Tubular supports tagging on Deals and Contacts. Twenty includes a Tag standard object that can be applied to Person, Company, and Opportunity records. We preserve all Tag labels as Twenty Tag records and apply them via Tag.targetObjectId and Tag.name during migration. Tag label deduplication ensures no duplicate tags are created in Twenty.

Tubular Tasks are associated with Leads and Deals. We transfer Task.title, due dates (Task.dueDate), owners (resolved by email to Twenty User), and completion status (Task.status). Recurring task patterns in Tubular are not supported in export and cannot be migrated; we document recurring patterns in the handoff notes so the admin can rebuild them in Twenty's Workflow engine.

Tubular activity logs attached to Deals and Contacts export as activity records via CSV or API depending on tier. Call logs map to Twenty Task with a custom taskType__c field set to Call. Email logs map to Twenty Note or Task with body content preserved. Meeting records map to Twenty Event with date, duration, and location. Where the Pro-tier export lacks API access, we coordinate manual CSV downloads of activities in dependency order after Deals are exported so that activity-to-deal links can be resolved.

Tubular User accounts and deal owners map directly to Twenty User by email match. We resolve every distinct owner referenced on Deal, Contact, Lead, and Task records before migration begins. Any Tubular owner without a matching Twenty User is placed in a reconciliation queue for the customer's admin to provision. Inactive Tubular users are migrated as inactive Twenty Users with records reassigned per the customer's preference.

Tubular PDFs and documents attached within deal flows can be extracted via UI scraping on Pro or API on Enterprise. We preserve file names, original upload timestamps, and the linked Deal name. Files are hosted as URL references in a custom Opportunity attachmentUrl__c field or as Note records with file links. We do not host or re-upload files; the original document URLs or the customer's exported file package are linked at the record level.

Tubular custom fields on Contacts and Deals migrate as custom fields on Twenty Person and Opportunity objects. We create all custom fields in Twenty's Settings → Data Model before migration, using field type mapping (text to text, number to number, date to date, checkbox to boolean, select to select). A pre-migration field creation checklist is delivered to the admin during the scoping phase so that the schema is ready before any CSV import begins.