Migrate from Leadtrekker Lead Management to HubSpot

Leadtrekker Lead maps 1:1 to HubSpot Contact. Standard fields (name, email, phone, address) transfer directly. The primary company name from Leadtrekker's company property becomes a lookup to a HubSpot Company record; if no Company record exists, a placeholder is created. Owner is resolved by email match against HubSpot users.

Leadtrekker stores company as a property on Lead. Where company name is present, FlitStack extracts it into a HubSpot Company record before Contacts are migrated, so AccountId lookups resolve correctly. Company-level fields (domain, industry, employee count) migrate as HubSpot Company properties where source data exists.

Leadtrekker users (sales agents) map to HubSpot Owners. FlitStack matches Leadtrekker user email addresses against HubSpot user emails. Unmatched users are flagged pre-migration so your team can either invite them to HubSpot or assign their records to a fallback owner.

Leadtrekker's lead source field (website form, referral, campaign) migrates to HubSpot's analytics source properties. Original source values are preserved as a custom property (Lead_Source__c) for reporting continuity when the default mapping does not capture the full label. If the lead source contains UTM parameters or campaign identifiers, those are retained alongside the standard mapping for downstream campaign attribution analysis.

Leadtrekker's binary lead status (active/inactive) does not map directly to HubSpot lifecycle_stage. FlitStack creates a custom property (Lifecycle_Status_Source__c) to preserve the original status, and the lifecycle stage is configured post-migration based on your sales process definition. If Leadtrekker records contain additional status values beyond the standard active/inactive states, those migrate as supplementary custom properties for manual review and stage assignment.

Leadtrekker's quote log (quote value, quote date, client name) migrates as custom properties on Contact or Deal depending on your HubSpot edition. HubSpot has no native quote object in the free or base CRM tier. We store quote value as Quote_Value__c, quote date as Quote_Date__c, and description as Quote_Notes__c. Full line-item quoting requires Sales Hub Starter+ or a third-party CPQ tool post-migration.

Leadtrekker notes attached to a lead become HubSpot Notes on the Contact record with original create timestamps preserved. Call outcomes and meeting notes migrate as HubSpot Activities — calls as type='CALL', meetings as type='MEETING'. Original owner and timestamp are preserved for audit continuity.

Leadtrekker's SMS/email notification events (triggered on lead assignment) have no HubSpot CRM equivalent at the contact level. We preserve the fact that a notification was sent and its timestamp as custom properties (Last_Notification_Sent__c, Notification_Type__c). The full notification content does not migrate as HubSpot does not store sent-notification history in the same model.

Leadtrekker's round-robin and source-based assignment rules are not data — they are workflow configuration. These do not migrate as records. Post-migration, your HubSpot admin recreates assignment logic using HubSpot Workflows with enrollment criteria based on lead source, contact property, or other qualifying conditions. The rebuilt workflows replicate the original assignment behavior using HubSpot's native automation engine.

Leadtrekker custom fields migrate to HubSpot Contact Properties. HubSpot creates custom properties with the same label and data type (text, number, date, dropdown). Multi-select or checkbox fields in Leadtrekker become text properties in HubSpot if the target property type is not available — your admin confirms the type in HubSpot's property settings before migration runs.

Leadtrekker's internal lead score is not a standard field but may exist as a custom field. FlitStack migrates it as a custom number property (Lead_Score__c) on Contact. HubSpot's native lead scoring (available in Sales Hub Pro+) is a separate feature that replaces the migrated value after configuration.

Leadtrekker captures UTM parameters and campaign names as lead properties. These migrate to HubSpot's analytics source properties for reporting continuity. We preserve the raw UTM string as Campaign_Source__c for reference and future campaign attribution analysis. The UTM data maps to HubSpot's hs_analytics_source_data fields to ensure existing reports continue to function after migration.

Leadtrekker file attachments on leads re-upload to HubSpot Files and attach to the Contact record. File size limits (20MB per file in HubSpot) apply. We re-host inline images from rich-text notes and preserve the original filename for traceability. Any attachments exceeding HubSpot's size limit are flagged for manual handling or alternative storage.

HubSpot's Createdate is set at import time by design. The original Leadtrekker create date is preserved as Original_Create_Date__c custom datetime property for reporting continuity. Updated timestamps migrate as Original_Last_Modified_Date__c, enabling change-audit reporting and helping teams understand when records were last modified in the source system.

Leadtrekker's internal lead ID is stored as Source_System_ID__c on the HubSpot Contact for traceability, deduplication, and delta-run matching. This field is critical for the delta-pickup window to identify records modified in Leadtrekker during cutover. During delta runs, FlitStack queries HubSpot for records where Source_System_ID__c matches and compares updated timestamps to pull only the changed fields.