Migrate from UPilot to Twenty CRM

UPilot Contact records map to Twenty CRM Person. The 360-degree contact view fields (name, email, phone, company association) migrate as standard Person fields. UPilot's inline task context—tasks displayed directly on the contact view—move to Twenty Activity records linked via the Person's id. We preserve the original UPilot contact id as a custom external_id field on Person for relationship reconciliation during migration.

UPilot Company records map directly to Twenty CRM Company. The one-to-many relationship between Company and Contacts is preserved via Twenty's Company-Person linked records. UPilot's Company domain and industry fields map to Twenty Company fields with equivalent names. Company must be imported before Person so that the Company lookup is satisfied at Person insert time.

UPilot Deals map to Twenty CRM Opportunity. Deal value, stage, expected close date, and associated contacts and company migrate. UPilot's per-deal contact role assignments (Decision Maker, Influencer, etc.) map to Opportunity Person relationships with role metadata. We use external ID matching on Company and Person to resolve the Opportunity's primary company and contact references during migration.

UPilot's colored pipeline stages per deal map to Twenty CRM Pipeline stages. We configure the Pipeline object in Twenty first, then map UPilot stage names to Twenty stage values. Stage order and probability percentages transfer to Twenty's stage configuration. If the customer has multiple UPilot pipelines, we create multiple Twenty Pipelines and assign them to Opportunity records via the pipeline reference.

UPilot Tasks migrate to Twenty CRM Tasks. In UPilot, task context displays inline within the 360-degree contact view; in Twenty, tasks link to Person or Company records via a foreign key relationship rather than embedding in the record. Task status, due date, assigned owner (by email match to Twenty User), and body text transfer directly. Task ordering in the timeline is preserved by setting the createdAt timestamp to the original UPilot timestamp.

UPilot's native Support module with ticket records and conversation threads maps to Twenty CRM Tasks used as a lightweight case proxy. Conversation threads from UPilot tickets migrate as Task comments linked to the parent Task record. Thread ordering is preserved by timestamp. If the customer has high ticket volume, we recommend configuring a custom 'Case' object in Twenty post-migration rather than relying on the Task proxy.

UPilot custom fields on Contact records map to custom fields on Twenty Person. We perform field-level type mapping (UPilot text to Twenty text, UPilot date to Twenty date, UPilot picklist to Twenty select) during the transform phase. Required flags are set on the destination fields only if the values are present for all migrating records; otherwise the field is created as optional and the admin sets required status post-migration.

UPilot custom fields on Deal records map to custom fields on Twenty Opportunity. Same type-mapping logic applies. If UPilot custom fields reference lookup values (e.g., a custom dropdown sourcing from another UPilot object), we resolve the foreign key at migration time and write the Twenty ID reference rather than a text string.

UPilot Owners map to Twenty CRM Users by email match. Any UPilot Owner without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on Deals and Tasks migrates by resolving the owner email to the newly provisioned Twenty User id.

UPilot's built-in forecast projection tied to pipeline stage probabilities is a derived calculation rather than a stored record type. We extract the stage probability percentages from UPilot and write them to custom fields on the corresponding Twenty Opportunity stages. The actual forecast view rebuilds in Twenty's reporting layer post-migration.

UPilot's two-way email sync maintains conversation threads linked to Contact records. We disable UPilot's email sync before migration to prevent new emails from creating orphaned threads. Historical email, call, and meeting records migrate as Activity records in Twenty linked to the corresponding Person. The activity type (email, call, meeting) maps to Twenty's activity type field, and the original timestamp preserves the timeline ordering.

UPilot marketing-specific records such as lead source and campaign associations are typically stored as custom fields or tags on Contact rather than separate objects. We migrate these as custom fields on Twenty Person or as tags depending on the customer's preference expressed during scoping.