Migrate from PHP CRM to Freshsales

PHP CRM contact records map directly to Freshsales Contact. The primary email address serves as the unique identifier and dedupe key during import. We resolve any parent Company relationship by looking up the Account created from the PHP CRM Company record and setting the Contact's target_account_id accordingly. Name, phone, address, and custom fields migrate field-by-field based on the discovery enumeration. Source Owner maps to Freshsales sales_owner_id by email matching.

PHP CRM Company records map to Freshsales Account. The Company domain or website URL becomes the Account's website field and is used as the dedupe key. Account is imported first, before any Contact, so that the target_account_id relationship is satisfied at Contact insert time. Industry, address, phone, and custom fields migrate per the discovery field map.

PHP CRM Deal records map directly to Freshsales Deal. Deal value, stage name, expected close date, owner assignment, and associated Contact and Company links migrate. We extract the actual stage names from the source PHP CRM instance and map them to Freshsales pipeline stage names, flagging any stages with no Freshsales match for customer decision. The deal's associated Contact and Company IDs resolve to the migrated Freshsales contact_id and target_account_id through our lookup tables.

PHP CRM Task records map to Freshsales Task with title, due date, status, priority, and description preserved. Task assignment migrates by resolving the PHP CRM owner ID to the Freshsales User via email match. Tasks linked to a Contact or Deal carry the resolved contact_id or deal_id reference from our parent-record lookup tables.

PHP CRM Note records migrate as Freshsales Note entries linked to the target entity (Contact, Account, or Deal) by resolved ID mapping. Note body and timestamp migrate; linked file attachments are extracted separately and handed to the customer for manual re-upload since PHP CRM stores attachments on the filesystem and not via API.

PHP CRM activity records (calls, emails, meetings) have schema variations per deployment. We enumerate the actual activity fields present in the source instance during discovery and map them to Freshsales Task (with TaskSubtype = Call for phone logs) and Event objects. Activity timestamp migrates as ActivityDate for Tasks and StartDateTime for Events. Email content migrates as a Note on the associated Contact if Freshsales does not have an email logging integration active.

PHP CRM allows custom pipeline definitions. We extract the pipeline names from the source instance and create matching Freshsales Pipelines during migration scoping. If multiple pipelines exist in PHP CRM, each becomes a separate Freshsales Pipeline with its own stage sequence.

Stage names and order vary by PHP CRM configuration. We extract the actual stage list from the source instance, map stage names 1:1 to Freshsales pipeline stages, and flag any stages with no destination match for customer approval before writing the migration mapping.

PHP CRM supports user-defined custom fields on standard objects with per-deployment uniqueness. We run a mandatory discovery phase enumerating every custom field present in the source instance, mapping each to a Freshsales custom field of equivalent type (text, number, date, picklist, checkbox). Freshsales custom fields are created in the target account before any data import begins. This enumeration step is non-optional because silent field drops during import are the most common migration error for PHP CRM sources.

PHP CRM User records map to Freshsales User by email match. We extract every distinct owner referenced on Contacts, Companies, Deals, and Tasks and match by email against the Freshsales User table. Owners without a matching Freshsales User go to a reconciliation queue; the customer's Freshsales admin provisions missing users before record import resumes.

PHP CRM tags stored on records migrate to Freshsales Tags. Tag vocabulary is per-instance, so we extract the full tag taxonomy from the source and create matching tags in Freshsales before record import. Tags with no Freshsales equivalent are flagged for customer decision.