CRM migration
Field-level mapping, validation, and rollback between Road Runner and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Road Runner
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
11 of 12
objects map 1:1 between Road Runner and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
3–6 weeks
Overview
Road Runner CRM stores standard objects — contacts, companies, deals, activities, and custom objects — with owner assignment and timestamps. Dynamics 365 Sales stores the equivalent data in Dataverse as accounts, contacts, leads, opportunities, and custom tables. We migrate all standard objects with original create dates and owner preservation, plus custom objects that map to Dataverse custom tables. Workflows, automations, email templates, and reports do not migrate — FlitStack exports definitions for your Power Automate rebuild but they must be rebuilt in Dynamics 365. The migration uses the Road Runner API for extraction and the Dynamics 365 Dataverse Web API for ingestion, with ExecuteMultiple batch operations to stay within the 60,000-request-per-user rate limit. A 24–48 hour delta window captures any records modified in Road Runner during cutover before go-live. During migration, we validate field lengths, required attributes, and pick-list consistency. Owner resolution uses email matching to preserve accountability. All records retain original create timestamps in a custom datetime field for historical continuity. After the delta window closes, a reconciliation report compares record counts and field-level integrity against the source environment.
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
Road Runner platform overview
Scorecard, SWOT, gotchas, and pricing for Road Runner.
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 Road Runner 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.
Road Runner
Contact
Microsoft Dynamics 365 Sales
Contact / Lead
1:manyRoad Runner contacts split into Dynamics 365 Lead and Contact based on deal status and engagement. Contacts with closed-won or closed-lost deals in Road Runner land as Dynamics 365 Contacts. All others route to Lead. Engagement history is preserved on both record types via activity pointer lookups.
Road Runner
Company
Microsoft Dynamics 365 Sales
Account
1:1Direct object-level map. Road Runner company hierarchies (parent/child) map to the Dynamics 365 Account.ParentId field. Multi-company associations on Road Runner contacts collapse to one primary AccountId plus Account Contact Relationship records for secondary companies. We also preserve the original industry and address fields on the Account, ensuring data completeness for downstream reporting.
Road Runner
Deal
Microsoft Dynamics 365 Sales
Opportunity
1:1Direct object map. Road Runner deal pipelines map to Dynamics 365 Sales Processes. Each pipeline becomes a Business Process Flow in Dynamics 365. Deal stage names map to Opportunity Stage values via value mapping; stage probabilities and forecast categories re-applied from Dynamics 365 defaults.
Road Runner
Pipeline Stage
Microsoft Dynamics 365 Sales
Opportunity Stage
1:1Stage names map value-by-value from Road Runner pipeline stages to Dynamics 365 Opportunity StageName pick-list values per Business Process Flow. Stage-entered timestamps from Road Runner are preserved as custom datetime fields on the Opportunity. Forecast category re-applied based on Dynamics 365 stage groupings.
Road Runner
Lifecycle / Status Field
Microsoft Dynamics 365 Sales
Custom Pick-list Field
1:1Road Runner lifecycle or contact status fields map to a custom pick-list field (LifecycleStatus__c) on both Lead and Contact in Dynamics 365. Dynamics 365 has no native lifecycle concept, so the custom field is required. Stage-change timestamps preserved as LifecycleStatusUpdated__c custom datetime.
Road Runner
Owner
Microsoft Dynamics 365 Sales
User
1:1Owner resolution by email match against Dynamics 365 User records. Road Runner owner IDs are matched to the corresponding Dynamics 365 User.FullName and UserId. Unmatched owners are flagged before migration — admin assigns a fallback owner or invites the user to Dynamics 365 before the run commits.
Road Runner
Activity (Call / Email / Meeting)
Microsoft Dynamics 365 Sales
Task / Email / Appointment
1:1Road Runner call activities map to Dynamics 365 Task records with Type='Phone Call'. Emails map to Email (emailtype) activities. Meetings map to Appointment records. Original timestamps, owner, and parent-record links (regarding objectid) are preserved. Attachments on activities re-uploaded as Dynamics 365 Notes or file attachments.
Road Runner
Note / Attachment
Microsoft Dynamics 365 Sales
Note / Attachment
1:1Road Runner notes and file attachments map to Dynamics 365 Note (annotation) records. Inline images in rich-text notes are extracted, rehosted as Dynamics 365 FileAttachments, and re-embedded. File size limits per Dynamics 365 attachment storage apply — large files flagged for admin review.
Road Runner
Custom Object
Microsoft Dynamics 365 Sales
Custom Table (Dataverse)
1:1Road Runner custom objects map 1:1 to Dynamics 365 custom tables (Dataverse). N:N relationships between Road Runner custom objects require junction tables in Dynamics 365. Custom table creation is scoped to the target license: Dynamics 365 Sales Professional limits custom tables to 15; Enterprise edition supports unlimited custom tables.
Road Runner
Product / Line Item
Microsoft Dynamics 365 Sales
Product / Opportunity Product
1:1Road Runner products map to Dynamics 365 Product records. Line items on Road Runner deals map to Opportunity Product records with quantity, unit price, and description. Product pricing uses the Road Runner price list; Dynamics 365 price list assignment happens post-migration during the rebuild phase.
Road Runner
Workflow / Automation
Microsoft Dynamics 365 Sales
Power Automate Cloud Flow
1:1Road Runner workflows, sequences, and triggers do not migrate. They must be rebuilt in Power Automate or Dataverse classic workflows. FlitStack AI exports the workflow definitions from Road Runner as JSON and delivers them as a rebuild reference for your Dynamics 365 admin or implementation partner.
Road Runner
Report / Dashboard
Microsoft Dynamics 365 Sales
Report / Power BI
1:1Road Runner reports and dashboards do not migrate. The underlying data migrates — so Power BI reports built post-migration will have access to the full historical dataset. We recommend scoping a Power BI implementation alongside the migration to replace Road Runner reporting with updated visuals.
| Road Runner | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Contact | Contact / Lead1:many | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Pipeline Stage | Opportunity Stage1:1 | Fully supported | |
| Lifecycle / Status Field | Custom Pick-list Field1:1 | Fully supported | |
| Owner | User1:1 | Fully supported | |
| Activity (Call / Email / Meeting) | Task / Email / Appointment1:1 | Fully supported | |
| Note / Attachment | Note / Attachment1:1 | Fully supported | |
| Custom Object | Custom Table (Dataverse)1:1 | Fully supported | |
| Product / Line Item | Product / Opportunity Product1:1 | Fully supported | |
| Workflow / Automation | Power Automate Cloud Flow1:1 | Fully supported | |
| Report / Dashboard | Report / Power BI1: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.
Road Runner gotchas
No public REST API for FSM record export
v1-to-v2 API rewrite requires complete config migration
Per-installation KV namespace schema varies
Bulk export not supported — we read incrementally
Attachment and media files are external to RoadRunner
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
Audit Road Runner schema and Dynamics 365 target license
FlitStack AI reads your Road Runner API to extract all standard and custom object definitions, field types, pick-list values, and relationship metadata. We cross-reference this against your target Dynamics 365 Sales license tier (Professional vs. Enterprise) to identify custom-table count limits, required custom field creation, and pipeline-to-Business Process Flow mapping needs. This audit produces the schema setup plan delivered to your Dynamics 365 admin before any data moves.
Resolve owners by email match
Road Runner owner IDs are matched to Dynamics 365 User records by email address. We generate an owner-resolution report listing every unique owner in Road Runner and their match status against Dynamics 365 users. Unmatched owners are flagged with a fallback-owner assignment rule or an invitation requirement. No record commits to Dynamics 365 without a resolved owner — orphan records are held until the admin resolves the mismatch.
Migrate accounts first, then contacts and leads, then opportunities
Dynamics 365 enforces a foreign-key dependency chain: accounts must exist before contacts reference ParentCustomerId, and contacts or leads must exist before opportunities reference them via opportunity-product relationships. FlitStack AI sequences the migration in dependency order — Accounts, then Contacts and Leads (routed by deal history), then Opportunities with pipeline and stage mapping. This prevents referential integrity errors at insert time.
Run sample migration with field-level diff
A representative slice of records — typically 100–500 spanning contacts, accounts, opportunities, and activities — migrates first. We generate a field-level diff comparing source values to destination field values so you can verify owner resolution, stage routing, lifecycle field values, and custom field population before the full run. You approve the sample output or request mapping adjustments before FlitStack AI commits to the full dataset.
Execute full migration with delta-pickup window and audit log
The full dataset migrates via Dynamics 365 Dataverse Web API using ExecuteMultiple batch requests paced to stay within the 60,000-request rate limit. A 24–48 hour delta-pickup window captures records created or modified in Road Runner during the cutover period. Every operation is logged to an audit trail, and one-click rollback reverts all migrated records if post-migration reconciliation reveals data integrity issues.
Platform deep dives
Road Runner
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Road Runner and Microsoft Dynamics 365 Sales .
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
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
Road Runner: Not applicable.
Data volume sensitivity
Road Runner 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 Road Runner to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Road Runner 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 Road Runner
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.
