Migrate your Agent Legend data
AI-powered lead-scoring CRM for real estate and mortgage agents that turns dormant contact databases into prioritized outreach pipelines using 1,600+ third-party data points.
In its favor
Why people choose Agent Legend
The signal that keeps Agent Legend on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Built-in AI scoring (Lily) eliminates manual lead prioritization by analyzing 270M U.S. adult profiles against 1,600+ third-party data points without requiring a data science team.
Circle prospecting automation handles recurring outreach at scale for real estate agents managing large geographically clustered databases of past clients and prospects.
Integrates natively with 500+ lead sources and popular real estate CRMs like Follow Up Boss and Lofty, reducing manual data entry across the stack.
Campaign builder and automated letter generation reduce the operational overhead of maintaining consistent client communication across thousands of contacts.
Monthly contact limits (250 Starter tier) are predictable, and annual billing waives the $499 setup fee, making cost planning straightforward for solo agents and small teams.
The per-contact pricing model ($0.40/contact) becomes expensive at scale as contact databases grow into the thousands, with no flat-rate unlimited tier available.
Lily AI features (lead scoring, data enrichment) are proprietary and do not export with contact records, meaning migration means losing the intelligence layer built over years.
Steep learning curve around campaign setup, Circle Prospecting configuration, and CRM integration workflows frustrates agents who expect faster time-to-value.
Limited multi-user collaboration features on lower tiers, with seat-based pricing creating friction for teams that need shared inbox or role-based access controls.
Customer support responsiveness is inconsistent, with some users reporting delayed responses when integration or billing issues arise.
Reasons to switch
Why people leave Agent Legend
The recurring reasons buyers give for replacing Agent Legend. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Agent Legend fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Agent Legend pricing overview
Agent Legend uses a hybrid model: an annual plan that waives the $499 setup fee, with per-contact usage billing at $0.40 on the Starter tier. Growth and Enterprise tiers are custom-priced based on contact volume and seat count. There is no published per-seat pricing, and the platform encourages annual commitment for cost savings.
Starter
Tier 1 of 3
$499 setup + usage-based (~$0.40/contact)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Agent Legend's schedule — see our quote-based pricing →
What gets migrated
Agent Legend object support
Object-by-object support for Agent Legend migrations. Per-pair details surface during scoping.
Contacts (Prospects)
Fully supportedContacts are the core object in Agent Legend. We migrate contact name, phone, email, address, and any standard properties directly. Custom fields are mapped individually. Lily AI scores do not export natively and are preserved as a custom Contact property on the destination CRM.
Campaigns
Mapping requiredAgent Legend Campaigns (Circle Prospecting, Campaign Builder) are workflow objects that contain sequencing, timing, and outreach templates. We map active campaigns to the equivalent automation or sequence object in the destination, noting that complex branching logic may require manual rebuild on the target platform.
Letters (Templates)
Mapping requiredLetter templates are stored as reusable outreach content tied to contact fields via merge tags. We export letter content and template logic but recommend re-attaching merge tags in the destination system as field names differ across CRMs.
CRM Integrations (Follow Up Boss, Lofty, 500+ lead sources)
Mapping requiredIntegration connections are account-level, not contact-level. We preserve integration configuration metadata but cannot transfer OAuth tokens. Webhooks and automated triggers must be re-authenticated and rebuilt in the destination CRM during the cutover window.
Users / Seats
Mapping requiredAgent Legend seat assignments are tied to billing tiers. We map user accounts to owner records in the destination, noting that seat count limits on Starter (1 seat) vs. Growth tiers may not map directly to the destination platform's user model.
Lead Sources
Fully supportedLead Sources represent the origin of a contact (portal, referral, website, etc.). We preserve Lead Source values as a standard contact property and map them to the equivalent field in the destination CRM.
Tags / Labels
Mapping requiredAgent Legend supports tagging contacts for segmentation. Tags migrate as a text array or multi-select field, depending on what the destination CRM supports natively.
Activity History (calls, emails, texts)
Mapping requiredCommunication logs and activity history are partially exportable. We map timestamp, type, and outcome fields. Rich media (call recordings, SMS content) may require separate export handling depending on the destination platform's storage model.
| Object | Support | Notes |
|---|---|---|
| Contacts (Prospects) | Fully supported | Contacts are the core object in Agent Legend. We migrate contact name, phone, email, address, and any standard properties directly. Custom fields are mapped individually. Lily AI scores do not export natively and are preserved as a custom Contact property on the destination CRM. |
| Campaigns | Mapping required | Agent Legend Campaigns (Circle Prospecting, Campaign Builder) are workflow objects that contain sequencing, timing, and outreach templates. We map active campaigns to the equivalent automation or sequence object in the destination, noting that complex branching logic may require manual rebuild on the target platform. |
| Letters (Templates) | Mapping required | Letter templates are stored as reusable outreach content tied to contact fields via merge tags. We export letter content and template logic but recommend re-attaching merge tags in the destination system as field names differ across CRMs. |
| CRM Integrations (Follow Up Boss, Lofty, 500+ lead sources) | Mapping required | Integration connections are account-level, not contact-level. We preserve integration configuration metadata but cannot transfer OAuth tokens. Webhooks and automated triggers must be re-authenticated and rebuilt in the destination CRM during the cutover window. |
| Users / Seats | Mapping required | Agent Legend seat assignments are tied to billing tiers. We map user accounts to owner records in the destination, noting that seat count limits on Starter (1 seat) vs. Growth tiers may not map directly to the destination platform's user model. |
| Lead Sources | Fully supported | Lead Sources represent the origin of a contact (portal, referral, website, etc.). We preserve Lead Source values as a standard contact property and map them to the equivalent field in the destination CRM. |
| Tags / Labels | Mapping required | Agent Legend supports tagging contacts for segmentation. Tags migrate as a text array or multi-select field, depending on what the destination CRM supports natively. |
| Activity History (calls, emails, texts) | Mapping required | Communication logs and activity history are partially exportable. We map timestamp, type, and outcome fields. Rich media (call recordings, SMS content) may require separate export handling depending on the destination platform's storage model. |
Gotchas
What to watch for in Agent Legend migrations
Issues we've hit on past Agent Legend migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Lily AI scores do not export from Agent Legend
CRM integration tokens and OAuth connections do not transfer
Contact-level per-message pricing creates billing risk on high-volume imports
Custom fields are not fully documented in the public API
Letter templates use proprietary merge tag syntax
| Severity | Issue |
|---|---|
| High | Lily AI scores do not export from Agent Legend |
| High | CRM integration tokens and OAuth connections do not transfer |
| Medium | Contact-level per-message pricing creates billing risk on high-volume imports |
| Medium | Custom fields are not fully documented in the public API |
| Low | Letter templates use proprietary merge tag syntax |
Leaving Agent Legend?
Where Agent Legend customers move next
12 destinations Agent Legend can migrate to.
How a Agent Legend migration works
Four steps, Agent Legend-specific
Connect
Bearer token (Zapier integrations); public REST API details are not fully documented publicly into Agent Legend. Scopes limited to read-only on the data we move.
Map
We translate Agent Legend-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Agent Legend quirks before production.
Migrate
Full migration with Agent Legend rate-limit handling. Rollback available throughout.
FAQ
Agent Legend migration FAQ
Answers to the questions buyers ask most during Agent Legend migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Agent Legend migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Agent Legend.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Agent Legend setup and destination — written quote back within a business day.