Migrate from Agent Legend to Freshsales

Agent Legend contacts map directly to Freshsales Contacts. The primary company association becomes the Contact's AccountId lookup. All standard name, email, phone, and address fields map one-to-one. Owner resolution runs by email match to Freshsales users before records land. Custom contact properties defined in Agent Legend are migrated as Freshsales custom fields if not already present. Original create dates are stored in Original_Create_Date__c for audit continuity.

Agent Legend stores a lifecycle stage on each contact record. Freshsales has a native Lifecycle Stage field on Contacts (plan-gated). If the destination is on Growth plan, FlitStack creates a custom pick-list field (Lifecycle_Stage__c) and maps values one-to-one with original stage labels preserved.

Agent Legend's Lead Intelligence Score (0–100) maps to Freshsales' native contact_score field if the destination runs Pro or Enterprise. On Growth plan, a custom Number field stores the score. The score is a point-in-time migration snapshot — Freshsales Freddy AI will overwrite it on next recalculation unless scoring is disabled.

Agent Legend companies map to Freshsales Accounts. Company name, domain/website, industry, employee count, and annual revenue fields map directly. Parent-child company hierarchies in Agent Legend become ParentId relationships in Freshsales Accounts. Multi-company contacts resolve to the most-recently-modified primary company on the Contact record.

Agent Legend deals map to Freshsales Opportunities. Each deal's stage maps to the Freshsales deal's stage pick-list value. If Agent Legend campaigns define separate pipelines, each campaign becomes a distinct Freshsales pipeline. Stage probability and forecast category re-applied from Freshsales defaults unless overridden in the migration plan.

Agent Legend campaigns map to Freshsales Campaigns. Campaign name, status, start/end dates, and budget fields migrate. Attribution tracking — which contacts were added by which campaign — migrates as Campaign Member records, preserving UTM and source attribution for Freshsales reporting.

Agent Legend call logs, emails, meetings, and notes map to Freshsales Sales Activities (type-scoped). Original timestamps, owners, and parent-record links are preserved. Agent Legend's auto-logged SMS messages map as Sales Activity with type='SMS' — the destination must have the SMS channel configured to display them in the timeline.

Agent Legend file attachments (property images, signed documents, lead documents) are downloaded and re-uploaded to Freshsales Files, associated to the parent Contact, Account, or Opportunity record. Freshsales file size limit is 25MB per file. Inline images embedded in Agent Legend notes are extracted and rehosted as separate file records.

Agent Legend custom objects map 1:1 to Freshsales custom objects. Custom object associations that use Agent Legend's N:N relationship model need Freshsales junction objects when the relationship is many-to-many. The migration plan surfaces these before the run so the destination-side custom object schema can be pre-created.

Agent Legend owner IDs resolve by email match against Freshsales users. Unmatched owners are flagged before migration — your team either invites them to Freshsales first or assigns their records to a fallback user. No record lands without a valid Freshsales owner. Active/inactive status is preserved as a flag on the Owner_Migrated_From__c field.

Agent Legend tags migrate as Freshsales tags. Tags on contacts, accounts, and deals attach to the corresponding Freshsales record. Freshsales applies tags as a flat list — tag hierarchy or grouping defined in Agent Legend collapses to a flat label set in Freshsales.

Agent Legend workflows, circle prospecting rules, and automated campaign sequences are not data records — they are configuration logic that does not exist in Freshsales' data model. FlitStack cannot migrate them. We export a configuration summary from Agent Legend as a rebuild reference for your Freshsales admin.