Migrate from LeadSimple to HubSpot

LeadSimple leads map to HubSpot contacts. The contact's name, email, phone, and address fields transfer directly. LeadSimple's 'Lead Name' field splits into HubSpot firstname and lastname properties. Original LeadSimple create date is preserved as a custom datetime field since HubSpot's Createdate is set at migration time.

LeadSimple properties have no direct HubSpot equivalent — they become a HubSpot custom object named 'Property'. Property address, type, occupancy status, and number of units become custom properties on the Property custom object. Each LeadSimple property record creates one Property custom object record linked to its associated contact.

LeadSimple units belong to properties and track occupancy, rent amount, and lease dates. Units map to a HubSpot custom object linked to the Property custom object via a custom association. Unit-level rent and lease-end dates become custom properties on the Unit custom object for reporting against deal pipelines.

LeadSimple pipelines model property lifecycle stages — Inquiry, Showing, Application, Lease, Renewal. Each LeadSimple pipeline becomes a HubSpot deal pipeline. Stage names map value-by-value to HubSpot deal stages within each pipeline. Stage-entry timestamps are preserved as custom datetime fields on the deal record.

Stage status values (Active, Won, Lost, On Hold) map to HubSpot deal stages. LeadSimple's 'Closed At' timestamp maps to HubSpot's closedate. For deals where LeadSimple has no close date, HubSpot's close date defaults to the migration date — flagged for admin review.

LeadSimple processes track property-management workflows like lease renewals and make-ready tasks. Processes map to a HubSpot custom object since HubSpot has no native process-tracking equivalent. Process stage, assigned user, and due date become custom properties. Process-task associations require a junction object in HubSpot.

LeadSimple contact custom fields store owner preferences, referral sources, and property-specific notes. Each LeadSimple contact custom field becomes a HubSpot contact custom property with the same field type (text, number, date, picklist). Picklist values are mapped value-by-value; multi-select picklists become HubSpot multi-checkbox properties.

LeadSimple's tag list on leads stores segmentation labels. Tags migrate to HubSpot as contact properties — single-value tags map to a HubSpot single-line text property; multi-value tags use HubSpot's multi-checkbox or a comma-separated text property. Tags are not HubSpot-native associations but are preserved for list-building in HubSpot.

LeadSimple owner IDs resolve to HubSpot users by email match. Unmatched owners are flagged before migration — teams either create HubSpot user accounts or assign records to a fallback owner. Owner resolution applies to contacts, properties, units, and deal records simultaneously.

LeadSimple's Annual Contract Value on leads maps to HubSpot deal amount. For leads that have not yet converted to a deal, the value is stored as a contact custom property (Annual_Contract_Value__c) until a deal is created in HubSpot's pipeline. The amount transfers as a numeric field; if empty, zero is used. This property also supports reporting on leads awaiting deal creation.

LeadSimple tracks lead source and referrer. Source Name maps to HubSpot's hs_analytics_source_data property on contacts. Referrer Name becomes a custom contact property (Referrer_Name__c) for segmentation. These are preserved for HubSpot reporting and list building. The source attribution is retained to maintain campaign performance visibility, while the referrer field supports lead source analysis and audience segmentation across HubSpot's tools.

LeadSimple engagement history (calls, emails, texts, notes) associates with leads. These map to HubSpot engagements — calls become HubSpot call records, emails become logged emails, and texts become HubSpot calls with a custom 'SMS' type property. Original timestamps and owners are preserved.