Migrate from Agent Legend to HubSpot

Agent Legend contacts map directly to HubSpot contacts. Standard properties (name, email, phone, address, city, state, zip, country) map to HubSpot's native contact properties field-by-field. Custom properties like Lily score and persona are written to HubSpot custom properties created before the migration run, ensuring each contact lands with its full data set intact.

Agent Legend's Lily predictive scoring (0–100) has no native HubSpot equivalent. FlitStack creates a custom number property (al_lily_score__c) on the Contact object and maps each contact's score from Agent Legend directly. Post-migration, HubSpot AI add-on or third-party scoring tools can replace or supplement this preserved score for ongoing lead intelligence.

Agent Legend stores lead type (First-Time Buyer, Investor, Downsizer, etc.) as a native contact property that drives outreach logic. HubSpot has no lead type field — FlitStack creates al_lead_type__c as a pick-list custom property and maps values one-by-one, preserving the full lead type taxonomy for segmentation and campaign targeting.

Agent Legend persona classifications (First-Time Buyer, Investor, Downsizer) drive campaign targeting across multi-channel sequences. HubSpot has no native persona field. FlitStack creates al_persona__c as a pick-list custom property and creates a HubSpot list per persona value so segmentation is immediately functional after migration completes.

Agent Legend call records with duration, outcome (connected, voicemail, no answer), and timestamp map to HubSpot's native call activity log attached to the contact record. Call outcome is stored in al_call_outcome__c as a custom pick-list because HubSpot call logs use free-text notes with no structured outcome field for filtering.

Agent Legend email campaign sends, opens, and clicks map to HubSpot email activities on the contact record. Email open and click counts from Agent Legend are preserved as custom number properties (al_email_opens__c, al_email_clicks__c) on the contact, maintaining engagement depth for reporting and segmentation after migration.

Agent Legend texts and ringless voicemails have no native HubSpot equivalent — HubSpot tracks emails, calls, and meetings natively but not SMS or voicemail activities. FlitStack creates al_text_sent__c, al_voicemail_sent__c, and al_last_text_date__c as custom properties to preserve the full multi-channel outreach history on each contact record.

Agent Legend campaign templates (multi-channel drip sequences with personalized content) do not export as data — the template definitions are stored in Agent Legend's application layer. FlitStack exports campaign template names and step definitions as a reference CSV so your HubSpot admin can rebuild sequences in HubSpot's Sequence tool.

Agent Legend company records map directly to HubSpot companies using direct field mapping for standard properties (name, domain, address, website). Agent Legend custom company properties (account_type, industry tags) become HubSpot custom company properties, preserving the full company profile for account-based segmentation.

Agent Legend contact tags are stored as a tag array on each record, enabling fast tag-based filtering and segmentation. HubSpot has no native tags array on contacts. FlitStack creates al_contact_tags__c as a long-text custom property storing tags as a comma-separated string, preserving tag data for reference, segmentation rebuilding, and workflow enrollment criteria.

Agent Legend appointment records from campaign responses map to HubSpot meeting activities on the contact record with original timestamps preserved. Agent Legend's appointments booked count per contact is stored as al_appointments_booked__c to maintain campaign ROI metrics for reporting after migration.

Agent Legend tracks which lead source each contact originated from (portal, referral, import, organic, paid, etc.). This maps directly to HubSpot's original_source_data property for native sources, or to a custom al_original_source__c property for non-standard Agent Legend source types that don't fit HubSpot's native source taxonomy.