CRM migration
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
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
9 of 10
objects map 1:1 between Agent Legend and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Agent Legend platform overview
Scorecard, SWOT, gotchas, and pricing for Agent Legend.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Microsoft Dynamics 365 Sales
Contact + Lead
1:manyAgent 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
Microsoft Dynamics 365 Sales
SystemUser
1:1Agent 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
Microsoft Dynamics 365 Sales
Account
1:1Agent 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
Microsoft Dynamics 365 Sales
msdyn_LilyScore__c (custom field on Contact + Lead)
1:1Lily'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
Microsoft Dynamics 365 Sales
msdyn_CampaignSequence__c (custom table) + Power Automate export
1:1Agent 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
Microsoft Dynamics 365 Sales
msdyn_LeadSource__c (custom Option Set on Lead)
1:1Agent 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
Microsoft Dynamics 365 Sales
Task + Email
1:1Agent 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
Microsoft Dynamics 365 Sales
SharePoint Document Location + Attachment
1:1Agent 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)
Microsoft Dynamics 365 Sales
msdyn_SourceIntegrationID__c (custom field)
1:1Agent 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
Microsoft Dynamics 365 Sales
Power Automate (manual rebuild required)
1:1Agent 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.
| Agent Legend | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Contact / Prospect | Contact + Lead1:many | Fully supported | |
| Agent / User | SystemUser1:1 | Fully supported | |
| Company / Account | Account1:1 | Fully supported | |
| Lily AI Score | msdyn_LilyScore__c (custom field on Contact + Lead)1:1 | Fully supported | |
| Campaign / Sequence | msdyn_CampaignSequence__c (custom table) + Power Automate export1:1 | Fully supported | |
| Lead Source | msdyn_LeadSource__c (custom Option Set on Lead)1:1 | Fully supported | |
| Communication Log / Email / Call | Task + Email1:1 | Fully supported | |
| Attachment / File | SharePoint Document Location + Attachment1:1 | Fully supported | |
| Integration ID (Lofty, Follow Up Boss) | msdyn_SourceIntegrationID__c (custom field)1:1 | Fully supported | |
| Agent Legend Workflow / Automation | Power Automate (manual rebuild required)1:1 | Fully supported |
Gotchas + challenges
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 gotchas
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
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Agent Legend
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Agent Legend and Microsoft Dynamics 365 Sales .
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Agent Legend and Microsoft Dynamics 365 Sales .
Object compatibility
All 8 core objects map 1:1 between Agent Legend and Microsoft Dynamics 365 Sales .
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Agent Legend: Not publicly documented.
Data volume sensitivity
Agent Legend doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Agent Legend to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Agent Legend
Other ways to arrive at Microsoft Dynamics 365 Sales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.