Migrate from Lead Perfection to HubSpot

Lead Perfection Job maps directly to HubSpot Deal. The job name becomes the Deal name. Amount, close date, and lead source from the Job metadata fields map to the corresponding HubSpot Deal properties. Original Lead Perfection job IDs are preserved as a custom property for traceability and delta-run de-duplication.

Lead Perfection stores the full customer name in a single customer_name field. During migration, FlitStack AI splits the value on the first space delimiter to populate HubSpot Contact firstname and lastname. Names with no delimiter land as a single firstname with lastname blank — flagged for review before the full run commits.

Lead Perfection Job Address stores line_1, line_2, and CSZ as separate fields. The CSZ field is parsed into HubSpot's city, state, and postal_code subfields. When the Job has no Company association, address data lands on the Contact record. If a Company record exists for the customer, the address is associated at the Company level and linked to the Contact.

Lead Perfection creates separate Job Phone records for each phone type (Phone, AltPhone1, AltPhone2). The first record with type 'Phone' maps to HubSpot Contact.phone. Additional phone types are stored as custom contact properties (alt_phone_1__c, alt_phone_2__c) since HubSpot Contact has no native multi-phone support. The original phone type label is preserved in the custom property name.

Each Lead Perfection Job Appointment maps to a HubSpot Event engagement. The original appointment.start_time becomes the Event start time; appointment.end_time (computed as start_time + 2 hours in Lead Perfection) becomes the Event end time. The appointment summary and notes fields land in the Event description. Original appointment IDs are stored as a custom property on the Event.

Lead Perfection Notes linked to Jobs via metadata.lead_perfection_id migrate as HubSpot Notes associated to the corresponding Contact or Deal. The original note content, timestamp, and Lead Perfection ID are preserved. Notes without a resolvable parent record are flagged and held for manual association before the full run.

Lead Perfection stores the sales rep name in Job.metadata.lead_perfection_salesperson. FlitStack AI resolves this against HubSpot users by email match (derived from the rep's user record name pattern or an explicit lookup table provided during discovery). Unmatched reps are flagged before migration — your team either creates HubSpot user accounts first or assigns records to a designated fallback owner.

HubSpot has no native field for storing the source system's internal ID. We create a custom text property (source_lead_perfection_id__c) on Contact, Company, Deal, Event, and Note objects. This ID enables delta-run de-duplication and supports rollback traceability if reconciliation finds discrepancies after go-live.

Lead Perfection stores lead source as Appointment.Source and sub-source as Appointment.SubSource in the Job object. Both values migrate — primary source maps to HubSpot's deal original source data property, and sub-source is stored as a secondary custom property. Your team configures HubSpot's source tracking behavior after go-live.

Lead Perfection product categories (window, siding, HVAC, solar, etc.) are industry-specific with no native HubSpot equivalent. These values migrate as a custom pick-list property on the Deal object (job_type__c). This property is available for HubSpot reporting and workflow enrollment after migration.