Migrate from The Customer Factor to HubSpot

The Customer Factor customers map directly to HubSpot contacts. Each customer record also creates or links to a HubSpot company record using the customer address data. If The Customer Factor stores multiple service locations per customer, additional addresses migrate as company address properties or contact properties.

The Customer Factor prospects become HubSpot contacts with a custom 'Prospect_Source__c' property set to 'The Customer Factor' for traceability. Prospects do not automatically become companies — they link to an existing company if an address match is found, otherwise they land as standalone contacts.

When The Customer Factor customers include company names, we extract those as HubSpot company records. The customer's billing address and service location address become the company's address properties. Parent-child company hierarchies in The Customer Factor map to HubSpot's parent company field.

Each The Customer Factor estimate becomes a HubSpot deal. The estimate total amount maps to deal amount. Line items in the estimate map to HubSpot line items tied to HubSpot products — if a product does not exist, we create a placeholder product record during migration. Estimate status (pending, accepted, declined) maps to a custom deal status property.

Job records in The Customer Factor represent completed service visits. We migrate job history as HubSpot engagements — completed jobs become meeting records with the original job date as the engagement timestamp. Job description fields become notes attached to the contact or deal.

HubSpot has no native invoicing object. Invoice records migrate as PDF file attachments on the associated contact or deal record. Invoice number, amount, and status (paid/unpaid) are preserved as custom properties on the contact. HubSpot Payments can be set up post-migration for future invoicing.

The Customer Factor's callback scheduling feature maps to HubSpot tasks. The task subject is set from the callback description, the due date from the callback date, and the owner from the email-matched user. Open callbacks migrate as open tasks; completed callbacks migrate as closed tasks with original completion date.

Any custom fields on The Customer Factor customer record become HubSpot contact custom properties. The property data type is inferred from the field content (text, number, date, picklist). If The Customer Factor uses pick-list custom fields, we create HubSpot pick-list properties and perform value-by-value mapping.

Custom fields on estimates in The Customer Factor migrate as custom properties on the corresponding HubSpot deal. The property data type is inferred from the field content, and pick-list values are mapped to HubSpot pick-list options. Fields that reference customer data are mapped after the customer-to-contact mapping is complete to avoid orphaned references. If the estimate includes line items, those are handled separately in the deal-to-line-item mapping.

Scheduled appointments in The Customer Factor become HubSpot events. The event start/end time, location (service address), and assigned user migrate. If the appointment includes notes or job details, those append to the associated contact record as a note.

The Customer Factor user accounts are matched to HubSpot users by email address. If a The Customer Factor user has no matching HubSpot user, their records are assigned to a fallback owner specified by your team before migration. We flag all unmatched owners in the pre-migration validation report.

Email and call logs from The Customer Factor migrate as HubSpot engagements — emails become email engagements, calls become call engagements, and logged communications without a type become notes. Original timestamps and owners are preserved. The engagement is linked to the associated contact record.