Migrate from PHP CRM to HubSpot

php-crm contacts map directly to HubSpot Contacts, preserving firstname, lastname, email, phone, mobilephone, jobtitle, and address fields. The primary_company_id foreign key is resolved to a HubSpot Company association after the companies load. Original created_at and updated_at timestamps are retained for audit, and we store the php-crm record ID as source_system_id for delta-run de‑duplication.

php-crm stores owner_id as a user reference. We resolve owner_id to HubSpot owner by matching php-crm user email against HubSpot user email. Unmatched owners are flagged before migration so your team can create HubSpot users first or assign to a fallback owner.

php-crm custom fields on contacts (beyond standard fields) map to HubSpot custom properties on the Contact object. We create each custom property in HubSpot with the matching field type: text for strings, number for integers, checkbox for booleans, date for dates, and picklist for enumerated values with value-by-value mapping.

php-crm companies map directly to HubSpot Companies. Standard fields — name, domain, industry, phone, address, employee count, annual revenue — map to HubSpot Company properties with the same names or close equivalents. php-crm stores parent_company_id for company hierarchies; we map this to HubSpot's parent_company_id property.

php-crm company custom fields migrate to HubSpot Company custom properties. We extract field definitions from php-crm's database schema (for flat-column custom fields) or EAV tables (for EAV-stored custom fields), then create HubSpot properties with the matching type before loading data.

php-crm deals map to HubSpot Deals. Fields including dealname, amount, closedate, and pipeline_id migrate directly. php-crm stores pipeline_id as a reference to php-crm's pipeline table; we map this to HubSpot's pipeline by matching pipeline names or IDs from your php-crm configuration export.

php-crm deal stage_id maps to HubSpot Deal stage via value mapping. Each php-crm stage_name becomes a HubSpot pipeline stage name. We preserve stage order, probability, and forecast category from HubSpot's stage configuration if available, or use the order from php-crm's stage table.

php-crm deals may have custom fields beyond the standard set. These migrate to HubSpot Deal custom properties following the same custom field translation process as contacts and companies. Deal-level custom fields often include product references, win/loss reasons, or billing terms.

php-crm call logs are migrated to HubSpot Call engagements via the HubSpot Engagements API, preserving call direction (inbound/outbound), duration in seconds, outcome disposition, and any notes attached. The original call timestamp is stored in hs_timestamp, and we link each Call engagement to its associated HubSpot Contact and Deal records using the associations API. Owner information is carried over from php-crm user records.

php-crm email logs are pushed into HubSpot Email engagements via the HubSpot Engagements API, copying the subject line, body (plain text or HTML), direction, and original email timestamp into hs_timestamp. Each Email engagement is associated with the corresponding HubSpot Contact and Deal records using the associations API, preserving the original sender and recipient details for full conversation continuity.

php-crm meeting records are imported as HubSpot Meeting engagements using the HubSpot Engagements API, retaining the meeting title, start and end timestamps, location or conference link, and outcome status. The original meeting datetime is stored in hs_timestamp, and each Meeting engagement is linked to its related HubSpot Contact and Deal records via the associations API, ensuring the meeting appears in the appropriate timeline.

php-crm notes map to HubSpot Notes attached to the relevant CRM records (Contact, Company, or Deal). We preserve note body, created datetime, and the associated record IDs. HubSpot notes display in the timeline of the associated record with the original author information.

php-crm file attachments are downloaded from the source storage (local filesystem for self-hosted, or cloud storage for php-crm cloud), then re-uploaded to HubSpot Files. Each file is associated with the relevant HubSpot record (contact, company, or deal) via the Files API. File size limits from HubSpot apply.

php-crm users are mapped to HubSpot Owners by email address. If a php-crm user email matches a HubSpot user email, we assign ownership directly. If no match exists, we flag the record and your team either creates the HubSpot user first or assigns records to a fallback owner before migration.

php-crm workflows and automation rules do not migrate. php-crm stores workflow definitions in its own database schema with different logic constructs than HubSpot Workflows. We export php-crm workflow definitions as a reference document so your HubSpot admin can rebuild them manually in HubSpot's Workflows tool post-migration.