Migrate from PHP CRM to Pipedrive

PHP CRM Contact records map directly to Pipedrive Person objects. We map standard fields (name, email, phone, address) using Pipedrive's name, email, phone, and address fields. PHP CRM custom fields on Contact require mandatory enumeration during discovery before any field-level mapping is written, as PHP CRM allows user-defined field names with no standardized taxonomy per deployment. The Person object in Pipedrive supports multiple email addresses and phone numbers; we map the primary contact field to the first value in Pipedrive's primary field and secondary values to additional data fields if present in the source.

PHP CRM Company records map to Pipedrive Organization. We map company name, domain, address, and industry fields directly. Organization is migrated first as a parent entity before Person records import so that the organization_id field can be resolved on each Person record during migration. PHP CRM custom fields on Company are enumerated during discovery and mapped to Pipedrive Organization custom fields created before import.

PHP CRM Deal records map to Pipedrive Deal. The deal title, value, expected close date, owner, and stage fields migrate directly. PHP CRM stores deal stage as a field value (standard or custom); we extract the distinct stage labels present in the source data, create the corresponding Pipedrive Pipeline and Stage structure before Deal import, and map each source stage label to the matching Pipedrive Stage ID during record import.

PHP CRM has no native pipeline object; pipeline structure is implied by deal stage field values. We extract all distinct stage labels used across Deals in the source instance and create a Pipedrive Pipeline with Stage entries matching the source labels. If the source has multiple distinct stage label sets (e.g., one set for direct sales and another for partner deals), we create multiple Pipedrive Pipelines and map each source record to the correct Pipeline ID during import.

Stage names and ordering are extracted from PHP CRM Deal records at migration scoping. We create matching Pipedrive Stage entries under the corresponding Pipeline, preserve stage order from source, and assign probability percentages based on the source stage values if numeric probabilities exist, or use standard deal-to-close probability curves if they do not.

PHP CRM Task records migrate to Pipedrive Activity records with type=Task. We map due date, assignee (resolved via Owner/User email matching), status, and linked entity (Person, Organization, Deal) via Pipedrive's deal_id and person_id fields. PHP CRM task content migrates as the activity note body. Task status (pending, completed) maps to Pipedrive's done flag.

PHP CRM Notes attach free-text content to any entity (Person, Organization, Deal). We map Notes to Pipedrive Activity records with type=Note, preserving the content as the activity body and linking to the target entity via the appropriate Pipedrive foreign key (person_id, org_id, deal_id) resolved after parent record migration.

PHP CRM Activity records use a variable schema per deployment. We enumerate every activity field present in the source instance during discovery, identify which represent calls (disposition, duration), emails (subject, body, direction), and meetings (start time, end time, location), and map them to the corresponding Pipedrive Activity subtypes. Any activity field that does not match a Pipedrive native field becomes a Pipedrive Activity custom field. This per-deployment enumeration step is mandatory; skipping it results in silent field drops for non-standard activity attributes.

PHP CRM User records map to Pipedrive Users. We resolve owners by email matching. Any PHP CRM Owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before Deal import resumes. Inactive or deleted PHP CRM users are flagged for decision: map to an inactive Pipedrive User (preserving historical assignment) or reassign to an active owner.

Tags in PHP CRM label records for segmentation. We extract the full tag vocabulary from the source instance, create corresponding Pipedrive Labels, and map each tagged record to the matching Pipedrive Label ID. Tag vocabulary is per-instance and non-standardized, so the full taxonomy is enumerated during discovery rather than assumed.

PHP CRM custom fields on all standard objects require mandatory discovery enumeration before any mapping is written. We enumerate every custom field name, data type, and object association in the source instance, then pre-create matching Pipedrive custom fields (text, number, date, picklist, checkbox) on the corresponding Pipedrive object before data import. PHP CRM stores field data in its own schema without standardized field naming; we match by semantic content (e.g., source field 'industry_type' on Company maps to Pipedrive Organization custom field 'industry_type') rather than by field name coincidence.

PHP CRM stores file attachments on the local filesystem (self-hosted) or configured cloud storage path. No documented API endpoint exists for attachment extraction. We export the attachment directory to local storage for customer review and advise re-uploading through Pipedrive's bulk file import tools post-migration. This is explicitly flagged as a manual post-migration step in the scope document.