Migrate from Delta Sales CRM to HubSpot

Delta's Lead and Contact objects both migrate into HubSpot Contact. Delta lead_status values map to HubSpot lifecycle_stage as a custom pick-list property (Lifecycle_Stage__c). No lead record is dropped — all historical leads land in HubSpot with their original create date preserved as Original_Create_Date__c.

Delta Contact maps directly to HubSpot Contact. Core fields including firstname, lastname, email, phone, jobtitle, and address transfer as direct property mappings. Delta's primary company association links to the HubSpot Company object through HubSpot's primary company association model. During migration, we validate that all required fields are populated and flag any records with missing email addresses for resolution before the final import commit.

Delta Company maps to HubSpot Company with domain/website, industry, employee count, and annual revenue as direct property transfers. Delta's parent-company hierarchy (where applicable) maps to HubSpot's parent company association using the parent_company_id field. Organizations with complex corporate structures benefit from this mapping approach, though circular references are flagged before migration to prevent data integrity issues in the HubSpot destination.

Delta Deal maps to HubSpot Deal with deal name, amount, close date, and owner resolving to HubSpot user by email match. The Delta pipeline and dealstage fields map to HubSpot deal pipeline and dealstage via value mapping per stage name — each Delta pipeline requires a corresponding HubSpot pipeline to be created first.

Delta Products migrate to HubSpot's Product Library. Product name, SKU, price, and description map directly. Product associations to Delta deals migrate as HubSpot Line Items linked to the corresponding HubSpot Deal, preserving the quantity and unit price per line item.

Delta stores activities as tasks with type (call, meeting, reminder), assignee, due date, and notes. These map to HubSpot CRM Tasks for standalone tasks and to HubSpot Engagements (call, email, meeting) where Delta stores communication logs with original timestamps and owner attribution preserved.

Delta's native invoicing and payment records have no native HubSpot equivalent. We create a Delta_Invoice__c custom object (or custom properties on Deal) to preserve invoice ID, amount, status, and payment date. Your team decides whether to link invoices to HubSpot deals or archive them externally.

Delta's dealstage pick-list values are mapped value-by-value to HubSpot dealstage names per pipeline. Probability and forecast category are applied based on HubSpot's stage defaults — your admin can override after migration. Stage-entered timestamps from Delta are stored as custom datetime properties.

Delta custom fields (tracked on leads, contacts, companies, deals) require corresponding HubSpot custom properties to be created before migration. We generate a custom property creation plan based on Delta's field list and data types. All custom property values transfer verbatim.

Delta file attachments on leads, contacts, companies, and deals re-upload to HubSpot's file manager. Each file is linked back to the originating record. File size limits from HubSpot apply (25MB per file); inline images in Delta notes are downloaded and rehosted.

Delta stores field-rep GPS coordinates per customer visit. HubSpot has no native GPS model — we store the last recorded visit date, visit count, and coordinates as custom properties on the associated HubSpot Contact or Company record. Beat-plan and route data is preserved as a JSON blob in a long-text custom property for reference.

Delta owner records (sales reps with roles and permissions) resolve to HubSpot Users by email match. Delta's role hierarchy (admin, manager, rep) has no direct HubSpot equivalent — roles and permissions must be manually assigned in HubSpot using HubSpot's native roles and teams model post-migration.