Migrate from Perfectview to Twenty CRM

PerfectView's Relation object is the primary carrier of both company and contact data. We split each Relation into one Company record (using the organisation name and business address) and one or more Person records (using the individual name, email, phone, and role fields). The split logic examines the Relation type, address type flags, and function fields to determine whether each field belongs in Company or Person. We validate split output against a sample of 50 live records before bulk migration runs. The original Relation ID is preserved in a custom field relation_original_id__c on both output records for cross-reference.

PerfectView Activities (calls, emails, meetings, tasks) map to Twenty's Timeline entries. We resolve the Activity type: calls become Tasks with TaskSubtype=Call, meetings become Events with start and end timestamps, task-type Activities become Tasks, and note-type Activities become Notes. Each Timeline entry is linked to the resolved Person or Company via the standard lookup. ActivityDate is preserved as the original timestamp. Owner resolution uses email-based matching against Twenty workspace members.

PerfectView Lead records (or Relations with Lead lifecycle stage) migrate as Person records in Twenty CRM with a custom pipeline stage field added to capture the original lead status. Lead source, lead score (if stored as a custom field), and owner assignment migrate to equivalent custom fields on Person. If Twenty's workspace-level pipeline is enabled, leads map to the relevant pipeline stage value.

PerfectView Cases (complaint management and support ticketing) migrate as Twenty custom objects named Case. We create the Case object via Twenty's /metadata API during the schema design phase, including custom fields for status, priority, assignee, and linked Relation. Conversation history migrates as Timeline entries on the Case custom object. If the customer prefers a simpler model, Cases can map to Opportunities with a Case Record Type.

PerfectView documents migrate as file attachments on the relevant Company or Person record in Twenty. We retrieve documents via the PerfectView API where enabled, falling back to the built-in bulk export function for bulk downloads. Document metadata (filename, upload date, uploader) is preserved as file metadata. Large documents (>10MB) may require chunked upload handling via Twenty's file API.

PerfectView Quotes migrate as Twenty CRM Opportunities with line item data stored as custom fields or a linked OpportunityLineItem-equivalent custom object. We create the custom line item schema during schema design, then import Quote header fields (quote number, total, status, validity date) to the Opportunity and line items to the linked custom object. Quote PDFs migrate as file attachments on the Opportunity.

PerfectView Invoice records migrate as a custom Invoice object in Twenty CRM, created via /metadata API. Invoice fields (number, date, amount, status, payment terms) map to custom fields on the Invoice object. Invoices are linked to the parent Company record via a lookup. Note that invoice numbers may require renumbering in Twenty because PerfectView uses its own sequential numbering scheme that may conflict with any existing Twenty numbering.

PerfectView custom fields on Relations and standard objects are discovered during the discovery phase by inspecting a sample export. We create equivalent custom fields in Twenty via the /metadata API before migration, handling field type mapping (text to text, date to date, numeric to number). Multi-select values in PerfectView map to multi-select picklist or text fields in Twenty depending on cardinality.

PerfectView custom object schemas are documented during discovery and replicated as custom objects in Twenty CRM using the /metadata API. Each custom object receives its defined fields, lookup relationships, and validation rules. Custom object records migrate after standard objects so that all parent lookups are resolved. The Twenty GitHub issue tracker shows the /metadata endpoint as the correct mechanism for custom object management.

PerfectView user records and owner assignments migrate as Twenty workspace members. We match PerfectView owners by email against the Twenty workspace. Any owner without a matching workspace member is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner-to-record links are preserved in the mapping file and reassigned to the matching workspace member.