Migrate from Agent Legend to Salesforce Sales Cloud

Lily lead scores require Salesforce custom field and do not feed Einstein scoring

Agent Legend's Lily scoring runs on 1,600+ third-party enrichment signals outside Salesforce. When records migrate, the Lily score lands as a custom number field (Lily_Score__c). Salesforce Einstein Lead Scoring, available at the Unlimited edition, uses Salesforce CRM data and activity signals to generate its own scores — it does not inherit Lily's methodology. If your team relies on Lily scores for rep prioritization, you must establish a transition period where Lily_Score__c drives outreach priority until Einstein scoring stabilizes on your migrated dataset. Building a Salesforce Flow that surfaces Lily_Score__c as a list view field is the fastest path to preserving the prioritization logic.

Circle prospecting logic has no native Salesforce equivalent and must be rebuilt

Agent Legend's circle prospecting defines geographic areas around target properties and automates multi-channel outreach to contacts within that radius. Salesforce has no native geo-radius campaign concept — you cannot create a Campaign that automatically enrolls contacts based on proximity to an address. FlitStack exports your circle definitions (center coordinates, radius, associated contacts) as a structured reference file. Your Salesforce admin rebuilds the geo-enrollment logic using Salesforce Maps (for visualization) and Sales Engagement Cadences (for sequence automation). This is manual configuration work outside the data migration scope.

Campaign sequences require Salesforce Sales Engagement rebuild

Agent Legend campaigns store multi-step messaging sequences (email, SMS, voice drop) with timing rules between steps. Salesforce's native Campaign object tracks campaign membership but does not execute outbound sequences — that requires Salesforce Sales Engagement (available at Unlimited and Agentforce 1 editions). Your Agent Legend sequence steps export as a CSV listing step type, timing, and content. Your Salesforce admin rebuilds each sequence as a Sales Engagement Cadence. Until rebuilt, Salesforce cannot replicate the automated follow-up cadence your team ran in Agent Legend.

Dual CRM records from Lofty and Follow Up Boss integrations require de-duplication

Agent Legend's native integrations with Lofty and Follow Up Boss may have created contact records that also exist in those CRMs. When migrating from Agent Legend, you may have duplicate records — one from Agent Legend's sync with Lofty, one from Agent Legend's sync with Follow Up Boss, and potentially one from a direct Lofty-to-Salesforce sync if that was active. FlitStack de-duplicates against email as the primary key, keeping the most recently modified record. Records with unique emails from each source merge into a single Salesforce Contact or Lead. Records with conflicting data (different names at the same email) are flagged for manual resolution before the migration commits.

Agent Legend's per-contact billing flag does not translate to Salesforce

Agent Legend charges $0.40 per contact communicated with, not per total contacts in the database. Salesforce has no equivalent per-contact billing model — you pay per user seat regardless of contact volume. If your Agent Legend costs were driven by outreach volume (contacts messaged per month), that cost model disappears in Salesforce. We preserve the Agent Legend contact count and monthly outreach volume as reference fields (Total_Contacts__c, Monthly_Outreach_Volume__c) so your finance team can model the Salesforce cost against the actual outreach volume before committing to the platform.