Migrate from LeadTrac to HubSpot

LeadTrac stores all person records in a single contacts table. Every LeadTrac contact maps directly to a HubSpot Contact record. First name, last name, email, phone, job title, and address fields map field-by-field to HubSpot's native contact properties. Records without an email address are flagged for manual review because HubSpot requires an email for contact deduplication.

LeadTrac allows limited custom fields per contact record. Any custom field defined in LeadTrac that has no direct HubSpot property equivalent is created as a HubSpot custom property (text, number, date, or pick-list type) before migration. The custom property API name follows HubSpot's camelCase naming convention. FlitStack creates these properties during the pre-migration schema phase.

LeadTrac companies map to HubSpot Companies. Company name, domain/website, industry, employee count, and annual revenue fields map directly. LeadTrac does not support company hierarchies, so HubSpot's Parent Company field is left blank. If a LeadTrac contact references a non-existent company, the company is created in HubSpot first, then linked.

LeadTrac deals map to HubSpot Deals. The deal name, amount, and close date map field-by-field. The deal's status pick-list value (e.g., Open, Won, Lost) maps to a HubSpot Deal Pipeline stage. If LeadTrac uses multiple deal stages beyond the default three, FlitStack creates a HubSpot pipeline and maps each LeadTrac status to the corresponding pipeline stage.

LeadTrac does not have a visual pipeline builder — deal status is a flat pick-list. FlitStack creates a HubSpot Deal Pipeline to give deals a visual representation. The LeadTrac deal status values become HubSpot pipeline stage names. If multiple LeadTrac deal types exist, each maps to its own HubSpot pipeline so stage values are scoped correctly.

LeadTrac stores PDFs and documents per contact or company record. These are downloaded from LeadTrac and re-uploaded to HubSpot Files, then attached to the matching HubSpot Contact or Company record. Files larger than 25MB are split if necessary. The original file name and any description stored in LeadTrac are preserved as metadata.

LeadTrac activity logs record calls, emails, SMS messages, and notes with timestamps and user attribution. Each activity type maps to the corresponding HubSpot engagement object (engagements API). Call activities map to HubSpot calls, emails to emails, meetings to meetings, and notes to notes. The original timestamp, owner, and body text are preserved. Subject lines are auto-generated from the activity type and date if not present in LeadTrac.

LeadTrac assigns records to users. HubSpot owners are HubSpot users. FlitStack resolves each LeadTrac user by email address against HubSpot user records. Users without a matching HubSpot account are flagged before migration; these records are assigned to a fallback owner specified by your team or remain unassigned for post-migration review.

LeadTrac groups and team assignments have no direct HubSpot equivalent. Group membership is preserved as a custom multi-checkbox or single-line text property on the contact record. HubSpot Teams must be configured manually in HubSpot settings before or after migration; FlitStack provides a team mapping export CSV.

If LeadTrac has custom objects beyond the standard contact/company/deal, these are mapped to HubSpot Custom Objects (available on HubSpot Professional and Enterprise tiers). Custom object associations in LeadTrac may require HubSpot custom association types. FlitStack surfaces the custom object schema before migration and creates the HubSpot custom object definitions in your portal.

LeadTrac tracks lead source and campaign attribution per contact. HubSpot's original source tracking is set at the contact level via hs_analytics_source. LeadTrac's custom source fields (e.g., utm_medium, referral_url) are migrated as HubSpot custom contact properties so the attribution data is preserved for reporting even if HubSpot's native source detection overwrites the original value.