Migrate from Market Leader to HubSpot

Market Leader contact records map directly to HubSpot contacts, preserving all standard fields including name, email, phone, address, and contact details. A custom property (ML_Source_ID__c equivalent) stores the Market Leader record ID for traceability and delta-run de-duplication. Each contact is validated for email format and checked for duplicates against existing HubSpot contacts before insertion.

Market Leader company records map to HubSpot companies with direct field alignment on company name, domain, address, industry, and employee count. Parent-child company hierarchies in Market Leader map to HubSpot's parent company association. Validation confirms each parent company exists in HubSpot before writing child records to maintain referential integrity.

Market Leader leads route to HubSpot contacts when they represent an individual prospect. Leads associated with an active transaction route to a HubSpot contact with a linked deal. The lead source field (Agent ID, Team ID, or marketing source) becomes a HubSpot contact property.

Market Leader agents are first-class objects that map to HubSpot users through email resolution. If a Market Leader agent email matches an existing HubSpot user, the agent record attaches to that user. When no HubSpot account exists for an agent, FlitStack creates a placeholder user and flags it for license provisioning before go-live. Agent-specific fields such as license number and team assignment become HubSpot user properties.

Market Leader teams map directly to HubSpot teams, preserving team-based assignment rules and reporting structures. Each Market Leader team becomes a HubSpot team, ensuring team-level lead routing is maintained after migration. Team-level lead routing configurations are documented for manual rebuild in HubSpot workflow settings.

Market Leader Transaction records map to HubSpot deals, with the transaction status field (Active, Pending, Under Contract, Closed, Cancelled) mapped to a corresponding HubSpot deal stage. Transaction amount, commission, and property address fields become HubSpot deal custom properties. Owner resolution follows the same email-matching logic used for agents and contacts.

Market Leader drip campaign definitions — step order, email content, delay intervals, and trigger conditions — do not have a native HubSpot equivalent that accepts direct import. FlitStack exports each campaign as a JSON reference document your HubSpot admin uses to recreate the logic in HubSpot's workflow builder.

Market Leader pre-written drip email content is exported as HTML files with step metadata. These files serve as copy and structure reference when rebuilding sequences in HubSpot Sales Hub or Marketing Hub. The emails themselves cannot be imported directly into HubSpot.

Real estate-specific fields in Market Leader (agent license number, MLS ID, agent ID, team ID) have no standard HubSpot equivalent. FlitStack creates matching HubSpot custom properties — text or number type — during the migration plan phase so they are ready before data lands.

Market Leader lead status values (New, Contacted, Showing, Offer Made, Under Contract, Closed) map to a combination of HubSpot lifecycle stage and deal stage. We document the full value-mapping table during discovery so stage probabilities are set correctly in the destination pipeline.

Market Leader call logs, meeting notes, and general notes migrate to HubSpot as engagement records. Call logs become HubSpot calls, meeting notes become HubSpot meetings, and free-form notes become HubSpot notes. Original timestamps, agent-owner associations, and related contact or deal links are preserved in the migrated engagement records.

File attachments associated with Market Leader contacts, leads, or transactions are downloaded and re-uploaded to HubSpot Files. Each file is linked back to its corresponding HubSpot contact or deal record via the file association API. File size limits per HubSpot's storage tier apply at the destination and are validated before upload.

Market Leader tracks lead source (Zillow, Realtor.com, IDX website, referral, etc.) as a contact property. These source values map to HubSpot's analytics source field, with custom source labels preserved as additional HubSpot contact properties for reporting continuity. The value-mapping table is delivered during discovery for validation before migration runs.