Migrate from Agent Legend to HighLevel

Agent Legend contacts migrate directly to HighLevel contacts. Every standard field — name, email, phone, address — maps to its HighLevel equivalent. Lily lead scores are preserved as a custom field (Lily_Score__c) since HighLevel has no native AI scoring engine. Tags assigned in Agent Legend migrate as HighLevel Tags.

Agent Legend company records map directly to HighLevel companies. Standard fields including company name, domain, industry, employee count, and address all transfer to their HighLevel equivalents. Agent Legend supports N:1 contact-to-company associations where multiple contacts belong to one company — this relationship structure aligns with HighLevel's company-contact model, preserving the organizational hierarchy during migration.

Agent Legend deal records (with pipeline stage, amount, close date, and owner) map to HighLevel Opportunities. Deal stage names are mapped value-by-value to HighLevel pipeline stages, and the deal's campaign source migrates as a tag or custom field on the Opportunity record.

Agent Legend campaigns — used to group contacts by source (Circle Prospecting, portal leads, referrals) — do not have a direct HighLevel equivalent. We map campaign names to HighLevel Tags and record them in a custom Opportunity Source field so reporting can still filter by original acquisition channel.

Lily's AI lead score (0–100) is a contact property with no native HighLevel equivalent. We create a custom Number field (Lily_Score__c) on the Contact object and populate it from Agent Legend's score data. This lets your team build Workflow conditions on score ranges without rebuilding the scoring logic from scratch.

Agent Legend Circle Prospecting tracks geographic and demographic assignment rules that determine which agents manage which leads based on location and property type. We migrate this data as a custom text field (Circle_Prospecting_Zone__c) on the contact record and apply a corresponding tag in HighLevel. This preserves the assignment context so your team can rebuild the geographic routing logic inside HighLevel Workflows.

Agent Legend activity history — including logged calls, emails, SMS exchanges, and notes — migrates to HighLevel Activities. Original timestamps, activity types, and assigned owner are all preserved during the transfer. HighLevel's Activity timeline displays these entries in chronological order on each contact record, maintaining the full interaction history.

Any custom fields you have configured on the Agent Legend Contact object are recreated as custom fields on the HighLevel Contact object before migration. Field type (text, number, date, picklist) is matched as closely as possible. We flag pick-list fields that need value-mapping setup.

Deal-level custom fields beyond the standard stage, amount, and close date migrate to custom fields on the HighLevel Opportunity object. We create these fields in HighLevel before the import run and validate that pick-list values align with your existing deal data. A pre-migration checklist ensures your HighLevel admin creates all required fields before data transfer begins.

Agent Legend tracks lead source — including portals like Zillow and Realtor.com, plus referrals and direct inquiries — as a contact property. These map to HighLevel's Lead Source pick-list values, and each unique source type also generates a tag on the contact for segmentation. Tags enable filtering in HighLevel Workflows and SmartLists beyond what the pick-list supports alone.

Agent Legend owner IDs are resolved to HighLevel user accounts by matching email addresses between the two systems. Any owner in Agent Legend without a corresponding HighLevel user account is flagged before migration begins. Your team must either create the missing HighLevel user account first or assign those records to a designated fallback owner to prevent orphaned records in the destination.

Files attached to Agent Legend contacts or deals are downloaded from the source system and re-uploaded to HighLevel's document storage. We preserve the original filename, upload date, and parent record association during the transfer so each file appears in the correct contact or opportunity record in HighLevel, maintaining document traceability.