Migrate from Onsite CRM to Twenty CRM

Onsite Contact records (name, email, phone, company association) map to Twenty People records. The Onsite contact-company relationship preserves as a People-Company link in Twenty. We deduplicate on email address during import. Phone number format normalization (stripping non-numeric characters) is applied before insert. Owner assignment is resolved by email lookup against Twenty Members provisioned before migration.

Onsite Company records map directly to Twenty Company records. The company name becomes displayName, and the company domain becomes the website field. We use name plus domain as the dedupe key. Company records are imported first to satisfy the Company-People lookup relationship at the moment of People insert.

Onsite Deal records map to Twenty Opportunity records. Deal name becomes opportunityTitle, deal value maps to amount, and the close date maps to closeDate. Pipeline stage names from Onsite map to Twenty Opportunity stage values that we configure in Settings before migration. We extract stage probabilities from Onsite if they are exposed in the export and apply them to Twenty stage configuration.

Onsite custom pipeline stages (varying by customer configuration) map to Twenty Opportunity stage values that the customer's admin configures in Settings → Data Model before import. We extract the customer's pipeline stage definitions from the Onsite UI during scoping and include them in the migration schema document. Stage order and probability percentages transfer as configuration notes for the admin to apply.

Onsite CRM call logs, SMS threads, and email records mapped as Activities migrate to Twenty Task or Note records depending on content type. Call records with disposition and duration migrate as Task records with the activity date and body preserved. Notes and meeting records migrate as Note records. Activity ordering is preserved by setting the activity timestamp. We flag any activity records that cannot be fully represented in the export as a post-migration reconciliation item.

Onsite Task records (follow-ups and reminders) migrate to Twenty Task records with Status, Priority, due date, and assignee preserved. Task assignment is resolved via email lookup against Twenty Members. Tasks with an Onsite owner who does not have a corresponding Twenty Member are placed in a reconciliation queue for the customer to resolve before final import.

Custom fields on any Onsite CRM object require pre-creation in Twenty before import. Customers typically have 3-15 custom fields covering business-specific attributes on Contact, Company, or Deal records. We document each Onsite custom field with its type, options, and object association, then create the corresponding Twenty custom field in Settings → Data Model before migration. Any Onsite fields with no direct Twenty equivalent are flagged for the customer's admin to either create the field or accept data loss.

Tags applied to Onsite Contacts or Deals migrate as Topics in Twenty (with TopicAssignment records linked to the parent People or Company) or as a multi-select custom field, depending on the customer's tagging taxonomy and usage. The customer chooses the strategy during scoping. We include tag normalization (removing duplicates and standardizing casing) in the import transform.

Onsite User records map to Twenty Member records referenced as owners on People, Company, and Opportunity objects. Users must be provisioned in Twenty Settings → Members before data import begins, as Twenty resolves owner references at the moment of record insert. We request customer-supplied screenshots of Onsite user list during scoping and match by email to the provisioned Twenty Members.

Onsite CRM does not appear to expose a structured file attachment or document management object in its UI-exported data. File attachments referenced in activity records may not appear in CSV exports. We flag this during scoping and recommend that the customer extracts files separately via the Onsite UI before cutover. No automated attachment migration is included in standard scope.