Migrate your PHP CRM data

Standard contact records with name, email, phone, and address fields. PHP CRM uses a REST API to create, read, update, and delete contact records. We map Contacts directly to destination CRM Contacts using email as the primary deduplication key.

Company/Account records store business entity data separate from individual contacts. We migrate Companies first as parent entities before importing associated Contacts to preserve the relationship.

Deal records represent sales opportunities linked to Companies or Contacts. PHP CRM stores deal value, stage, expected close date, and owner assignment. We map Deals to destination Opportunities and preserve stage associations via Pipeline mapping.

Task records include due dates, assignees, status, and linked entities (Contact, Company, Deal). We map Tasks directly and preserve entity linkage using destination ID matching after parent record migration.

Notes attach free-text content to any entity (Contact, Company, Deal). We migrate Notes as rich text blocks linked to the target entity by our computed relationship mapping.

Activity records track interactions (calls, emails, meetings) with timestamps and outcome data. PHP CRM activity schemas vary by deployment. We enumerate the actual activity fields present in the source instance before mapping to destination Activities.

Pipelines are containers for deal stages. PHP CRM allows custom pipeline definitions. We map Pipeline names 1:1 and handle stage renaming during migration scoping.

Stage names and order vary by PHP CRM configuration. We extract the actual stage list from the source instance and map to destination stage names, flagging any stages with no destination match.

PHP CRM supports user-defined custom fields on standard objects. Custom field names and types vary per deployment. We enumerate all custom fields during discovery and build field-level mappings to destination custom properties.

User records store login credentials, roles, and assignment ownership on Deals and Tasks. We map Users to destination Users by email matching, flagging inactive or deleted source users.

Tags in PHP CRM label records for segmentation. Tag vocabulary is per-instance. We extract the full tag taxonomy and map tags to destination labels or custom properties.

File attachments on records are stored on the self-hosted file system or cloud storage path. PHP CRM does not expose a documented attachment export endpoint. We export attachments to local storage for manual re-upload or advise customers to export via the admin panel.

Email templates are stored in the PHP CRM application layer without a documented API export method. We do not migrate email templates automatically; customers recreate them in the destination CRM.

Automated workflow rules and triggers are PHP CRM application logic not exposed via API. We do not migrate automations. Customers must rebuild workflows in the destination CRM post-migration.