Migrate from UPNIFY CRM to Twenty CRM

UPNIFY Client records map directly to Twenty Person. Standard fields (name, email, mobile phone, company association) migrate 1:1. Custom client fields map as key-value pairs into Twenty's custom field infrastructure. We sequence Person import after Company to satisfy the company relationship. Spanish-language field names in UPNIFY's API responses are normalized to English equivalents during transformation.

UPNIFY Company records map 1:1 to Twenty Company. Company is imported before Person to establish the parent record for the company-person relationship. Domain, address, industry, and size fields map to their Twenty equivalents. Multi-branch companies stored as separate UPNIFY Company records migrate as separate Twenty Company records.

UPNIFY Opportunities map to Twenty Opportunities with the stage mapping provided by the customer during scoping. Pipeline stage names and IDs from UPNIFY's customizable stage configuration are mapped to Twenty stage values via a customer-supplied stage-mapp table. Opportunity amount, close date, owner, and company association migrate directly. Notes and comments attach to the Opportunity record in Twenty.

UPNIFY Prospects represent pre-qualified leads in a separate object from Clients. We assess each Prospect's lifecycle stage and business context to determine whether it belongs as a Person record (unqualified lead) or an Opportunity (qualified deal) in Twenty. Prospect lifecycle-stage values that do not map directly are preserved as a custom field for the customer's admin to assign meaning to post-migration.

UPNIFY Quotations carry product line items, pricing, currency, and embedded exchange-rate metadata as a nested array. The multi-currency metadata is flattened into a single price field during transformation — we extract the applicable rate at quotation date and compute a normalized amount. If Twenty's Opportunity model is sufficient for the customer's quoting workflow, quotations merge into Opportunities as custom fields. If a separate Quote custom object is needed, we pre-create it with line-item fields before migration.

UPNIFY Products under Catalogs migrate to a Twenty Custom Object named Product with fields for name, SKU, description, and price. Stock-level data is not consistently populated in UPNIFY and is flagged as absent during scoping. Products are imported before Quotations so that product references resolve during quotation migration.

Goals track team or user-level sales targets with period, target value, and owner assignment. We migrate Goals as a Twenty Custom Object with period, target value, owner, and status fields. Goals are user-scoped so we resolve the owner email to the corresponding Twenty workspace member. If Twenty's standard objects suffice for the customer's goal-tracking workflow, Goals migrate as Note records attached to the relevant user.

Calendar entries including tasks, reminders, and appointments migrate to Twenty Task and Event records with owner, due date, status, and description preserved. Completed versus open status maps directly. Recurring tasks are migrated as individual Task records with a custom recurrence flag. Task assignment resolves the UPNIFY owner email to the corresponding Twenty workspace member.

Tags applied across UPNIFY Clients, Companies, and Opportunities are exported per object. In Twenty, we create a custom multi-select picklist field per object (e.g., client_segment, company_industry_tag) and populate it with the source tag values. Tag vocabulary is preserved during migration and the customer decides whether to normalize or expand the tag taxonomy post-migration.

Custom fields on UPNIFY Clients, Companies, and Opportunities map to Twenty custom fields of equivalent type (text, number, date, dropdown). We pre-create all destination custom fields in Twenty's Data Model before any data import, following Twenty's requirement that fields must exist before CSV import. Type mismatches (e.g., a UPNIFY dropdown with an unmapped option) are flagged and resolved with the customer before migration.

UPNIFY Users are resolved by email address to Twenty workspace members. Active versus inactive status is preserved, but UPNIFY role and permission sets do not map to Twenty's role model and require manual reassignment post-migration. We flag any UPNIFY user without a matching Twenty member for the customer admin to provision.

UPNIFY Flow prepaid task bundles (Flow 200 at $89 for 200 tasks) operate on a volume model distinct from seat-based CRM pricing. Flow tasks, process stages, timing controls, and SLA escalation rules do not have a native equivalent in Twenty and are not migrated. We export Flow task data as a structured CSV inventory for the customer's admin to review and recreate as Twenty workflow steps or manual tasks.