Migrate from PHP CRM to Twenty CRM

PHP CRM Contact records map to Twenty People. We map standard contact fields (name, email, phone, address) directly and enumerate every active custom field present on the Contact object during discovery before writing any field mapping. The Twenty People object uses a flat address structure; PHP CRM address sub-fields (street, city, state, postal code, country) concatenate into the Twenty address fields. PHP CRM contacts linked to Companies receive a CompanyId lookup resolution after the Companies phase completes.

PHP CRM Company records map directly to Twenty Company. Company is migrated before People so that the Company relationship (WorkSpaces in Twenty) is available for resolution during People import. The Twenty Company object supports industry, employee count, annual revenue, website, and address fields mapped from equivalent PHP CRM fields. Custom fields on Company are enumerated during discovery and mapped field by field.

PHP CRM Deal records map to Twenty Opportunity. The deal name, value, expected close date, and owner assignment transfer directly. Deal stage names in PHP CRM map to Twenty pipeline stages, which we pre-create in the destination workspace before the Opportunity import phase. If PHP CRM has multiple pipelines, each becomes a separate Twenty pipeline.

PHP CRM pipeline definitions map to Twenty pipeline containers. We extract the pipeline list from the source instance during discovery and create matching Twenty pipelines with the same pipeline names. Pipeline creation in Twenty happens before any Opportunity records are imported so that stage assignment is valid at insert time.

PHP CRM stage names and order map to Twenty Stage records under each Pipeline. We extract the actual stage list from the source instance, preserving the sequence order and probability percentages where present. Any stages with no matching Twenty stage name are flagged as unmapped and held for the customer admin to resolve before Opportunity import.

PHP CRM Task records map to Twenty Task. Due date, assignee, status, and linked entity (Contact, Company, Deal) transfer directly. We resolve the assignee by matching PHP CRM owner email to Twenty User during the Users phase. The linked entity reference (Contact, Company, or Deal) resolves after parent record IDs are established in the destination system.

PHP CRM Notes attach free-text content to any entity (Contact, Company, Deal). Notes migrate as Twenty Note records linked to the target entity (People, Company, or Opportunity) via the computed relationship mapping after parent records are established. Note body transfers as rich text where PHP CRM stores it; plain text note bodies migrate as-is.

PHP CRM Activity records track interactions (calls, emails, meetings) with timestamps and outcome data. Activity schemas vary by PHP CRM deployment. We enumerate the actual activity fields present in the source instance during discovery and map call activities to Twenty Task with TaskSubtype=Call, meeting activities to Twenty Event or Task, and email activities to Twenty Note or Task depending on whether the email body is substantive. We flag any activity fields with no Twenty equivalent during discovery for customer decision on retention or exclusion.

PHP CRM custom fields on standard objects map to Twenty custom fields on the equivalent standard objects (People, Company, Opportunity, Task). Each PHP CRM deployment has a unique custom field inventory; we run a mandatory discovery phase enumerating every custom field on every standard object before writing any field mapping. Custom field types (text, number, date, picklist, checkbox) map to typed Twenty fields, and any unsupported field types are flagged for the customer admin to address before migration.

PHP CRM user records map to Twenty User by email matching. Owners assigned to Deals and Tasks are resolved via the User mapping. Any PHP CRM owner without a matching Twenty User (inactive or deleted source users) is flagged in a reconciliation queue for the customer admin to provision before record import resumes.

PHP CRM tags stored as multi-checkbox properties migrate to Twenty custom multi-select picklist fields on the equivalent standard object. Tag vocabulary is per-instance; we extract the full tag taxonomy from the source and map each distinct tag value to a Twenty picklist value or a separate Tag entity depending on how the customer intends to use tags post-migration.