Migrate from Upvise to Twenty CRM

Upvise contacts map directly to Twenty People records. Email is the unique identifier — we use it for de-duplication during import. Contacts without an email are imported with a generated placeholder address and flagged for review before the full migration run commits.

Upvise company records map 1:1 to Twenty Companies. The domain field (company.website) serves as the unique reference when linking People records via companyId. Multi-contact companies in Upvise link to the same Twenty Company record — no duplication occurs during import, preserving the original relationship structure.

Upvise deal data (deal name, amount, stage, close date, owner) maps to Twenty Opportunities. Pipeline stages from Upvise become Twenty Opportunity stage pick-list values — we map them value-by-value and flag any stage with no direct equivalent for your team to confirm the target state.

Upvise tasks migrate as Twenty Tasks. The task body, due date, status, and assigned user all transfer. Tasks are linked to their parent People, Companies, or Opportunities record via Twenty's relation field system — we map the parent reference during import to preserve context.

Upvise notebook entries map to Twenty Notes with the full note body preserved. Notes in Twenty can be attached to People, Companies, Opportunities, and custom objects — we restore the target record link from Upvise's note association data. Inline images embedded in notes are extracted separately, rehosted to Twenty Files, and the link is updated in the note body before migration completes.

Upvise Jobs (a field-service/work-order module) has no direct Twenty equivalent. We map Job name to Opportunity.name, Job amount to Opportunity.amount, and Job status to a custom Opportunity stage. Field-service-specific fields (priority, location, assigned technician) become custom fields — your admin confirms the schema before migration runs.

Upvise Assets (equipment, inventory items) require a custom object in Twenty since Twenty has no native asset management module. We create an Assets custom object via the /metadata API, define its fields from Upvise's Asset schema, and link Assets to their associated Company records using a relation field. Your admin reviews field labels and confirms the schema before data loads.

Upvise Maintenance records (service tickets, work orders) map to a Maintenance custom object in Twenty, created via the metadata API. Scheduled date, completion status, and linked Asset/Job references transfer as fields and relations — your team confirms the target object name and field labels during planning.

Upvise custom fields defined in the Options menu per module become Twenty custom fields on the corresponding object (People, Companies, Opportunities, or the custom objects above). Field type is preserved: text, number, date, select, multi-select, and URL map to their Twenty equivalents. Pick-list values require value-mapping setup when the target is a select field.

Upvise file attachments on contacts, companies, jobs, or tasks are downloaded from Upvise's storage and re-uploaded to Twenty Files. Each file attaches to its parent record (People, Companies, or Opportunities) using Twenty's file relation model. Inline images in notes are extracted, rehosted, and linked back into the note body.

Upvise user records resolve against Twenty workspace members by email address match — this is the only reliable link between Upvise owner IDs and Twenty assignees. Records with no matching email are flagged before migration so your team either invites the user to Twenty first or assigns to a fallback owner.

Upvise Timesheet and Expense records have no direct equivalent in Twenty's core schema. We create Timesheet and Expense custom objects via the metadata API, mapping hours/amount, date, and linked user/company references. Your admin reviews field labels and confirms the schema before data loads.

Upvise custom form layouts (PDF and Excel exports) are a presentation-layer construct with no data model counterpart. The form fields map to Upvise custom fields, which we migrate as Twenty custom fields. The PDF/Excel layout itself cannot migrate — we recommend exporting a sample form as a reference for your admin to recreate in your preferred document tool.