Migrate from PHP CRM to Salesforce Sales Cloud

PHP CRM Contact records map directly to Salesforce Contact. We use the contact's email address as the external ID and dedupe key during import. The contact's linked Company in PHP CRM must resolve to a Salesforce AccountId before Contact insert, which requires Company migration to precede Contact migration. Any source contact without a company link is inserted as a Contact with no AccountId and flagged in the reconciliation report.

PHP CRM Company records map to Salesforce Account. Company name becomes Account Name, domain fields map to Website, and industry data maps to Industry picklist. Account is the first object imported because every Contact has an AccountId foreign key. We handle Companies without contacts as standalone Account records.

PHP CRM Deals map to Salesforce Opportunity. Deal value maps to Amount, expected close date to CloseDate, deal owner to OwnerId via email matching against the User table, and deal stage to StageName via a stage-mapping table we build during scoping. Deals linked to a source Company map to an AccountId we resolved from the Account import phase.

PHP CRM's pipeline definitions map to Salesforce Record Types on Opportunity, each paired with a corresponding Sales Process that restricts available StageName values. We extract the pipeline names and stage sets from the source instance and configure equivalent Salesforce Record Types before Opportunity import begins.

PHP CRM stage names and probabilities migrate to Salesforce Opportunity Stage values with matching probability percentages rounded to Salesforce-allowed integers. Stages with no direct Salesforce equivalent are mapped to the nearest available StageName and flagged in the mapping document for customer review.

PHP CRM Task records map to Salesforce Task with Status, Priority, ActivityDate, and Description preserved. Task assignment migrates by resolving the PHP CRM owner ID to Salesforce OwnerId via email matching. Task linked entities (Contact, Company, Deal) resolve via the Salesforce IDs computed during the parent record import phase.

PHP CRM Notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. Note body transfers as plain text or rich text depending on what the source export contains. If the customer used HTML-formatted notes, we preserve the HTML and let Salesforce render it in its note editor.

PHP CRM Activity records (calls, emails, meetings) map to Salesforce Task (for calls and emails) and Event (for meetings) based on the activity type field. Each activity type in PHP CRM is enumerated during discovery and mapped individually because PHP CRM activity schemas vary by deployment. Activity timestamps preserve ordering in the Salesforce activity timeline.

PHP CRM custom fields on any standard object are enumerated during discovery and mapped to Salesforce custom fields of equivalent type. Text fields map to Text, numeric fields to Number, dates to Date, and picklists to Picklist. We prepend the source object name to the custom field name to avoid naming collisions (e.g., Industry__c from the Account object). Custom field types are validated against the source export before Salesforce field creation begins.

PHP CRM Users referenced as Deal and Task owners map to Salesforce User records by email address matching. We extract the complete owner list from source records and reconcile against the Salesforce destination org's User table. Owners with no matching Salesforce User are held in a provisioning queue for the customer's admin to create before record import resumes.

PHP CRM tags are per-instance vocabulary labels applied to any record. We extract the full tag taxonomy from the source and map tags to a Salesforce custom text field (for high-cardinality vocabularies) or a picklist (for controlled vocabularies under 300 values). The customer selects the strategy during scoping.

PHP CRM stores file attachments on the local server filesystem or configured cloud storage path, not through a documented API endpoint. We cannot programmatically extract attachments. We export attachment filenames and storage paths to a CSV for the customer's IT team to re-upload manually using Salesforce Files Connect or the native Salesforce file upload interface post-migration.