CRM migration

Migrate from Agent Legend to Microsoft Dynamics 365 Sales

Field-level mapping, validation, and rollback between Agent Legend and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .

Agent Legend logo

Agent Legend

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

90%

9 of 10

objects map 1:1 between Agent Legend and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Agent Legend stores a specific blend of lead-scoring intelligence — its Lily AI assigns scores against 1,600+ third-party data points across 270 million U.S. adult records — plus circle prospecting campaigns, contact-level communication logs, and agent productivity data. The platform runs as a standalone AI-driven prospecting layer with native integrations into Lofty, Follow Up Boss, and 500+ lead sources rather than a full CRM. Dynamics 365 Sales, built on Microsoft Dataverse, provides a structured schema with Account, Contact, Lead, Opportunity, and Task as primary tables plus configurable custom tables for Agent Legend properties that have no native equivalent. We extract contacts with full contact-card fields, agent profiles with email addresses for user resolution, campaign sequence definitions, Lily AI scores, lead source attribution, and activity history. Those records map into D365 Contact, Account, Lead, and custom tables (msdyn_AgentLegendScore, msdyn_CampaignSequence). Power Automate flows, circle prospecting sequences, and AI-agent configurations do not migrate — they are exported as JSON definitions for your D365 admin to rebuild inside Power Automate and Dynamics Sales Insights. The migration runs against the D365 Web API (v9.2) using upsert logic keyed on Source_System_ID__c so re-runs are idempotent. A 24–48 hour delta-pickup window closes the gap on any records modified in Agent Legend during the cutover window.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Agent Legend logo

Agent Legend

What's pushing teams away

  • 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.

Choosing

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

What's pulling them in

  • Deep Microsoft 365, Teams, and Outlook integration makes Microsoft Dynamics 365 Sales a natural fit for Microsoft-first organizations already invested in that ecosystem
  • Sales Enterprise and Premium tiers offer unlimited custom tables and advanced AI-driven forecasting and predictive analytics not available in lower tiers
  • Professional tier pricing at $65 per user per month offers a lower entry cost than Salesforce for SMB teams with straightforward CRM needs
  • Flexible customization options allow businesses to build bespoke apps, tailor forms and views, and integrate with other Dynamics 365 modules
  • Microsoft Copilot AI tools are embedded directly into the sales workflow on Enterprise and Premium, automating routine tasks and providing deal intelligence

Object mapping

How Agent Legend objects map to Microsoft Dynamics 365 Sales

Each row shows how a Agent Legend object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Agent Legend

Contact / Prospect

maps to

Microsoft Dynamics 365 Sales

Contact + Lead

1:many
Fully supported

Agent Legend contacts with an established sales relationship (stage: active, customer, or past client) map to D365 Contact. Prospects without a D365 Opportunity map to Lead so the qualification workflow triggers correctly. Split runs on Agent Legend's stage field; unmatched stages route to Lead by default.

Agent Legend

Agent / User

maps to

Microsoft Dynamics 365 Sales

SystemUser

1:1
Fully supported

Agent Legend agents carry email addresses and role assignments. We resolve each agent email against D365 SystemUser by email match. Unmatched agents receive a flagged record and fallback owner assignment; your admin invites them to D365 or assigns to a migration placeholder user.

Agent Legend

Company / Account

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

Agent Legend company records (name, domain, industry, employee count, annual revenue) map directly to D365 Account fields. Parent-company hierarchies in Agent Legend map to Account.ParentAccountId. Multi-company associations per contact collapse to a primary AccountId with additional accounts stored as AccountContactRelationships.

Agent Legend

Lily AI Score

maps to

Microsoft Dynamics 365 Sales

msdyn_LilyScore__c (custom field on Contact + Lead)

1:1
Fully supported

Lily's 0–100 score has no D365 native equivalent. We create a custom Number field (msdyn_LilyScore__c) on both Contact and Lead so the score travels with the record regardless of whether the contact qualifies to a Lead or Contact. Score-assigned date preserved as msdyn_LilyScoreDate__c.

Agent Legend

Campaign / Sequence

maps to

Microsoft Dynamics 365 Sales

msdyn_CampaignSequence__c (custom table) + Power Automate export

1:1
Fully supported

Agent Legend circle prospecting campaigns and drip sequences do not map to any native D365 object. We create msdyn_CampaignSequence__c as a custom table storing sequence name, step count, cadence, and source attribution. Sequence definitions are also exported as a JSON workbook for your admin to rebuild inside Power Automate or Dynamics Sales Engagement.

Agent Legend

Lead Source

maps to

Microsoft Dynamics 365 Sales

msdyn_LeadSource__c (custom Option Set on Lead)

1:1
Fully supported

Agent Legend tracks up to 500+ lead sources (Zillow, Realtor.com, referrals, etc.). D365 Lead has a native leadsourcecode field but it supports a limited picklist. Sources map to a custom Option Set (msdyn_LeadSource__c) on the Lead entity; Agent Legend's full source list is preserved value-by-value.

Agent Legend

Communication Log / Email / Call

maps to

Microsoft Dynamics 365 Sales

Task + Email

1:1
Fully supported

Agent Legend communication history (emails sent, calls logged, SMS threads) migrates as D365 Task records with Type='Email' or Type='Call'. Original timestamps and agent-owner resolved via email match. High-volume SMS logs migrate as Task records with subject prefix '[SMS]' for filtering.

Agent Legend

Attachment / File

maps to

Microsoft Dynamics 365 Sales

SharePoint Document Location + Attachment

1:1
Fully supported

Agent Legend file attachments (property flyers, mortgage pre-approval letters, campaign assets) re-upload to D365's SharePoint-integrated document management. Files re-associated to the parent Contact or Account record via absolute URL reference stored in a custom SharePoint_URL__c field.

Agent Legend

Integration ID (Lofty, Follow Up Boss)

maps to

Microsoft Dynamics 365 Sales

msdyn_SourceIntegrationID__c (custom field)

1:1
Fully supported

Agent Legend stores IDs from upstream integrations (Lofty contact ID, Follow Up Boss tag). These migrate as msdyn_SourceIntegrationID__c on Contact for traceability. The field also enables delta-run de-duplication — if an Agent Legend record with the same integration ID already landed in D365, it updates rather than duplicates.

Agent Legend

Agent Legend Workflow / Automation

maps to

Microsoft Dynamics 365 Sales

Power Automate (manual rebuild required)

1:1
Fully supported

Agent Legend automations — circle prospecting triggers, lead-routing rules, Lily-triggered follow-ups — do not have a D365 native equivalent. We export workflow definitions as a JSON configuration file that your Power Automate admin can use as a rebuild reference. Migration carries data only; automations are not transferred.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Agent Legend logo

Agent Legend gotchas

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

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales gotchas

High

Professional tier 15-table custom table limit blocks migrations

High

October 2024 pricing increase applies at renewal for all customers

Medium

Custom fields must be created in the UI before API writes

Medium

Power Platform request limits apply to bulk migrations

Medium

Activity records orphaned to inactive owners fail silently

Pair-specific challenges

  • Lily AI scores require a custom field — no native D365 equivalent

    Agent Legend's Lily assigns a proprietary 0–100 score against 1,600+ third-party data points. Dynamics 365 Sales has no built-in field for this score — it uses Dynamics 365 Sales Insights scoring which operates on behavioral signals, not Agent Legend's enrichment data. We create msdyn_LilyScore__c as a custom Number field on both Contact and Lead so the score travels with records regardless of qualification status. Your reporting team should treat this as a reference metric rather than a live-updating D365 field.

  • Prospecting sequences and circle campaigns do not transfer to D365

    Agent Legend's Campaign Builder and Circle Prospecting sequences are proprietary workflow definitions that have no D365 equivalent. Dynamics 365 Sales does not include a native multi-step cadence engine — the closest built-in tool is Sales Engagement (a separate licensed add-in) or Power Automate. We export campaign definitions as a structured JSON workbook that maps each step type (email, call, SMS, wait) to a Power Automate template structure. Your admin uses this as a rebuild reference; the migration itself carries data only.

  • D365 API rate limits require pacing across migration batches

    Dynamics 365 Dataverse Web API enforces 60,000 requests per user per 5-minute window. Agent Legend data exports can generate high-volume upsert batches that risk throttling. FlitStack AI paces API calls using application-user credentials with separate allocation pools, implements exponential backoff on 429 responses, and chunks record batches to 200 records per API call — the D365 Web API's optimal batch size. We surface any throttled records for retry before final validation.

  • Lead source attribution with 500+ sources needs a custom Option Set

    Agent Legend integrates with over 500 lead sources — Zillow, Realtor.com, mortgage rate aggregators, and direct referral networks. D365 Lead's native leadsourcecode field supports a limited picklist that cannot accommodate this volume. We create msdyn_LeadSource__c as a custom Option Set on the Lead entity, mapping Agent Legend's source name to the Option Set value. If your D365 admin uses the native leadsourcecode for a subset of sources, we can merge both fields during migration.

  • Power Automate flows triggered by Agent Legend integrations need manual rebuild

    Many Agent Legend customers connect the platform to Lofty and Follow Up Boss via Zapier or native webhooks. When Agent Legend records migrate to D365, those upstream Zapier triggers no longer fire against the new environment. We export Zapier step definitions as a configuration reference. Your integration admin rebuilds the Zapier-to-D365 connection using D365's built-in connector, replacing the Agent Legend trigger with a D365 Contact or Lead trigger.

Migration approach

Six steps for a successful Agent Legend to Microsoft Dynamics 365 Sales data migration

  1. Schema audit and custom field provisioning in D365

    FlitStack AI runs a pre-migration audit against your D365 Dataverse environment to identify existing tables, Option Sets, and field constraints. We provision the custom fields (msdyn_LilyScore__c, msdyn_LilyScoreDate__c, msdyn_AgentStage__c, msdyn_LeadSource__c, msdyn_CampaignSequence__c) and custom table before any data movement begins. You receive a schema setup checklist confirming each field's data type, security level, and form placement so your D365 admin can confirm before we proceed.

  2. Export and profile Agent Legend records

    We extract Agent Legend contacts, companies, agent profiles, campaign definitions, activity logs, and integration IDs via the Agent Legend API. Records are profiled for duplicates (matching on email + phone), stale records (no activity in 18+ months flagged for archival decision), and Lily-score distribution. A pre-migration data quality report identifies records that need enrichment or deduplication before they land in D365.

  3. Resolve agent-to-user ownership by email

    Agent Legend agents are matched against D365 SystemUser records by email address. Unmatched agents are flagged on a pre-migration ownership report with two resolution paths: invite the agent to D365 before migration or assign their records to a fallback D365 user. No record migrates without a resolved OwnerId — this prevents ownerless records that would be invisible in D365's security model.

  4. Run sample migration with field-level diff

    A representative slice of 100–500 records — spanning contacts across Lily-score ranges, companies with parent-child relationships, campaign sequences, and activity logs — migrates first. We generate a field-level diff comparing source values against D365 field values so you can verify Lily-score mapping, lead-source mapping, and account-contact resolution before the full run. You sign off on the diff before we proceed to production migration.

  5. Full migration with delta-pickup window

    The full dataset migrates in ordered sequence: Accounts first (for foreign-key resolution), then Contacts and Leads split by Agent Legend stage, then custom sequence records, then activities. A delta-pickup window of 24–48 hours after initial load captures any Agent Legend records modified during the cutover period. The audit log records every upsert operation, and one-click rollback is available if reconciliation identifies record count or field-value discrepancies above your agreed threshold.

  6. Deliver workflow export and rebuild reference

    Once data migration is validated, we deliver the campaign-sequence JSON workbook and Zapier configuration export. Your Power Automate admin uses these files to rebuild Agent Legend automations inside D365's workflow engine. We provide a rebuild priority ordering — contact nurturing sequences first, then lead-routing rules — so business-critical automations restore before lower-priority sequences.

Platform deep dives

Context on both ends of the pair

Agent Legend logo

Agent Legend

Source

Strengths

  • Lily AI lead scoring provides actionable prioritization without requiring technical setup or third-party data pipelines.
  • Circle Prospecting automates recurring geographic outreach, saving agents an estimated 19.7 hours per month on manual database sorting.
  • Native integrations with Follow Up Boss, Lofty, and 500+ lead sources reduce duplicate data entry across the real estate agent stack.
  • Predictable per-contact pricing with annual billing option that waives the $499 setup fee for qualifying teams.
  • Campaign response rates of 28–55% significantly exceed industry averages of 2–6%, validating the AI-driven targeting approach.

Weaknesses

  • Per-contact pricing scales poorly at high volume with no unlimited tier, making the platform expensive for large databases.
  • AI intelligence (Lily scores, enrichment data) does not export, meaning years of lead prioritization data are lost on migration.
  • Limited public API documentation and unclear rate limiting create challenges for custom automation and migration tooling.
  • Single-seat Starter tier restricts team collaboration, pushing teams toward higher tiers for shared access.
  • Customer support responsiveness is inconsistent according to third-party reviews, which complicates issue resolution during migration.
Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

Destination

Strengths

  • Native integration with Microsoft 365, Teams, Outlook, and SharePoint for unified productivity workflow
  • Unlimited custom tables and complex workflows on Enterprise tier enable deep customization for complex sales processes
  • AI-driven predictive analytics and deal intelligence on Enterprise and Premium tiers help sales teams prioritize pipeline
  • Dataverse unified data layer provides a consistent API and data model across all Dynamics 365 and Power Platform apps
  • Strong security model with Field-Level Security and Record Ownership rules for governance-conscious enterprises

Weaknesses

  • Sales Professional tier caps custom tables at 15, creating a migration ceiling for highly customized SMB environments
  • October 2024 pricing increases of $15 per user across all tiers apply to existing customers upon renewal
  • Implementation typically requires costly certified partners, adding 30–50% to total project cost
  • Updates and platform releases can disrupt customizations and plugins, requiring regression testing after each wave
  • Non-Microsoft integrations require additional configuration or middleware, limiting flexibility for heterogeneous tech stacks

Complexity grading

How hard is this migration?

Standard CRM migration. All 8 core objects map 1:1 between Agent Legend and Microsoft Dynamics 365 Sales .

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Agent Legend and Microsoft Dynamics 365 Sales .

  • Object compatibility

    A

    All 8 core objects map 1:1 between Agent Legend and Microsoft Dynamics 365 Sales .

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Agent Legend: Not publicly documented.

  • Data volume sensitivity

    B

    Agent Legend doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Agent Legend to Microsoft Dynamics 365 Sales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Agent Legend to Microsoft Dynamics 365 Sales data migrations

Answers to the questions buyers ask most during Agent Legend to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Agent Legend to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Agent Legend to D365 migrations complete in 48–72 hours for under 50,000 records. Larger setups with 200,000+ records or multiple custom tables (Lily score, campaign sequences, integration IDs) extend to 5–10 days. The longest single step is custom field provisioning and D365 admin sign-off on the schema setup checklist before data movement begins — typically 2–3 business days.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Agent Legend.
Land in Microsoft Dynamics 365 Sales , intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day