CRM migration
Field-level mapping, validation, and rollback between PlanPlus Online and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
PlanPlus Online
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
6 of 8
objects map 1:1 between PlanPlus Online and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
3-5 weeks
Overview
PlanPlus Online lacks a documented public REST API, which means all migration data must be extracted via the web interface's CSV export and sync connector dumps. We sequence the export by pulling calendar events and tasks first, then contact and company records, followed by opportunity pipeline data and custom fields. We preserve Franklin Covey priority quadrants and goal hierarchies as custom Contact or Company properties in Dynamics 365. Sync connections to Google and Microsoft 365 do not carry over and are documented for manual reconnection in the destination. Deal stages and pipeline structure map to Microsoft Dynamics 365 Sales Process and Opportunity Record Types, and the stage names require explicit mapping since there is no shared stage vocabulary between the two platforms. We do not migrate workflows, automations, or forms; we deliver a written inventory of these for the customer's admin to rebuild in Dynamics 365.
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
PlanPlus Online platform overview
Scorecard, SWOT, gotchas, and pricing for PlanPlus Online.
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 PlanPlus Online 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.
PlanPlus Online
Contact
Microsoft Dynamics 365 Sales
Contact
1:1PlanPlus Online Contact records map directly to Dynamics 365 Contact. All standard fields (name, email, phone, address, job title) migrate 1:1. Franklin Covey priority quadrants and any goal hierarchy links export as key-value custom properties and are mapped to custom Contact fields in Dynamics 365. If the contact has a linked Company in PlanPlus Online, the AccountId lookup resolves at migration time using the Company-to-Account mapping table. Sync connection status and calendar subscription settings are not migrated; they are documented for manual reconfiguration in Dynamics 365.
PlanPlus Online
Company
Microsoft Dynamics 365 Sales
Account
1:1PlanPlus Online Company records map to Dynamics 365 Account. Company name, industry, size classification, and address fields migrate 1:1. Links between Contacts and Companies in PlanPlus Online are preserved via a mapping table in the destination, where each Contact's parentcustomerid_account lookup points to the resolved Account. Company-level goal hierarchies and mission statements map to custom Account fields. Businesses without the Business Edition have no Company records; in those cases, Contacts migrate without a parent Account lookup.
PlanPlus Online
Deal (External Opportunity Portal)
Microsoft Dynamics 365 Sales
Opportunity
1:1PlanPlus Online Deal records map to Dynamics 365 Opportunity. Stage names from PlanPlus Online's pipeline structure do not share a vocabulary with Dynamics 365's default StageName picklist, so we create an explicit mapping table during scoping. The PlanPlus Online deal value and close date map to Amount and CloseDate. If PlanPlus Online tracks a custom probability percentage per stage, we map it to StepStatus or store it as a custom field. Opportunity ownership resolves by matching the PlanPlus Online owner email to a Dynamics 365 User record.
PlanPlus Online
Calendar Event
Microsoft Dynamics 365 Sales
Appointment (Activity)
1:1Calendar entries including appointments and all-day events export via the Microsoft 365 or Google sync connector and are processed as ICS or CSV records. They map to Dynamics 365 Appointment (Activity) records with StartTime, EndTime, Location, and Subject preserved. Attendee lists from PlanPlus Online calendar events map to ActivityParty records linked to the Appointment. If an event is linked to a Contact or Company in PlanPlus Online, the Regarding lookup resolves to the migrated Contact or Account.
PlanPlus Online
Task
Microsoft Dynamics 365 Sales
Task
1:1Tasks export with priority, due date, status, and assignment. The Franklin Covey priority quadrant (urgent/important matrix) is stored as a custom property in PlanPlus Online and maps to a custom picklist field on the Dynamics 365 Task. Linked subtasks from PlanPlus Online map as child Task records using the ParentTaskId lookup in Dynamics 365. Task assignment migrates by resolving the owner email to a Dynamics 365 User record. Incomplete tasks carry their original due date; completed tasks carry their completed date as ActivityDate.
PlanPlus Online
Project
Microsoft Dynamics 365 Sales
Project (Custom) or Task
lossyPlanPlus Online Projects export with status, milestones, and task breakdowns. Projects do not have a native Microsoft Dynamics 365 Sales equivalent, so we map them to either a custom Project object (if the customer licenses Dynamics 365 Project Operations or creates a custom entity) or as a parent Task hierarchy with milestone Tasks and sub-task items. Project Summary Reports published as webpages export as static HTML files and are delivered as a document package for manual re-upload to SharePoint or Dynamics 365 portals.
PlanPlus Online
Custom Field
Microsoft Dynamics 365 Sales
Custom Field
lossyCustom fields created within PlanPlus Online export as flat key-value pairs from the CSV export. We map them to equivalent custom fields in Dynamics 365, inferring field type from the data format (text to Single-Line Text, dates to Date fields, numeric values to Whole Number or Decimal). Fields with no direct match are flagged for manual review during the scoping phase. The maximum custom field count in Microsoft Dynamics 365 Sales varies by edition; we verify the destination edition's limits before migration.
PlanPlus Online
User/Owner
Microsoft Dynamics 365 Sales
User
1:1PlanPlus Online User accounts map to Dynamics 365 User records by email address. We extract every distinct owner referenced on Contact, Company, Deal, and Task records and match by email against the destination org's User table. Any PlanPlus Online owner without a matching Dynamics 365 User is placed in a reconciliation queue; the customer's admin provisions the missing users before record import resumes. Inactive PlanPlus Online users are flagged for the customer to decide whether they are provisioned as inactive Users in Dynamics 365.
| PlanPlus Online | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal (External Opportunity Portal) | Opportunity1:1 | Fully supported | |
| Calendar Event | Appointment (Activity)1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Project | Project (Custom) or Tasklossy | Fully supported | |
| Custom Field | Custom Fieldlossy | Fully supported | |
| User/Owner | User1: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.
PlanPlus Online gotchas
No public API means no automated migration pipeline
Data export blocked for delinquent accounts
Planner Edition lacks sync and export infrastructure
Auto-renewal with annual price adjustment
Time zone settings must be correct before sync setup
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
Account status verification and export sequencing
We verify that the PlanPlus Online account has no delinquent invoices before beginning any migration work, since PlanPlus Online may restrict data export for accounts with overdue payments. We then sequence the CSV export in dependency order: calendar events and tasks first (because they are the most granular and have no upstream dependencies), followed by contact and company records, then opportunity pipeline data, and finally custom fields. We provide the customer with a step-by-step export checklist tailored to their PlanPlus Online edition (Planner, Essentials, Professional, or Business). For Planner Edition accounts, we document the export path separately since it lacks the team export features of higher tiers.
Data quality audit and custom field mapping
We audit the exported CSV files for completeness, consistency, and data quality before any transformation begins. This includes identifying duplicate contact records, verifying that all owner emails correspond to identifiable users, confirming that date formats are consistent, and flagging any custom fields with ambiguous content. We build the custom field mapping table during this phase, inferring Dynamics 365 field types from the PlanPlus Online data and flagging any that require manual type decisions. The customer reviews and approves the mapping table before transformation scripts are written.
Dynamics 365 schema configuration
We configure the destination Dynamics 365 environment before any data is imported. This includes creating any required custom fields on Contact, Account, and Opportunity objects, configuring Sales Processes and Record Types to match the PlanPlus Online pipeline structure, and setting up the stage-to-stageName mapping table. We create a custom picklist field for Franklin Covey priority quadrants and any other PlanPlus Online-specific taxonomy that the customer wants to preserve. All configuration is deployed to a Dynamics 365 Sandbox first for validation, not directly to production.
Sandbox migration and reconciliation
We run a full migration into a Dynamics 365 Sandbox using production-like data volume to validate the mapping, identify any record-rejection issues caused by validation rules or field-level security, and produce a reconciliation report. The customer's admin reviews 25-50 spot-checked records against the PlanPlus Online source and signs off on the schema and mapping before production migration begins. Common issues caught at this stage include required fields on Account that are empty in PlanPlus Online, date fields with invalid formats, and picklist values that are not whitelisted in the destination org's field configuration.
Production migration in dependency order
We run production migration in record-dependency order. Accounts are imported first (from PlanPlus Online Companies). Contacts are imported second with parentcustomerid_account resolved from the Account mapping table. Opportunities are imported third with ownerId resolved by email match and stageName mapped from the stage mapping table. Tasks and Appointments are imported fourth via Dynamics 365's Bulk API with parent-record resolution. Custom fields are imported last as additional updates to the previously imported records. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and sync connection handoff
We freeze PlanPlus Online writes during cutover, run a final delta migration of any records modified during the migration window, then enable Dynamics 365 as the system of record. We deliver a sync connection inventory document listing every Google, Microsoft 365, and Outlook connection that must be reconfigured manually in Dynamics 365, along with the steps to do so. We deliver a workflow and automation inventory for the customer's admin to review. We do not rebuild PlanPlus Online workflows, forms, or automations as Dynamics 365 Power Automate flows or Sales Processes within the migration scope; that is a separate engagement. We support a one-week hypercare window for reconciliation issues.
Platform deep dives
PlanPlus Online
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 PlanPlus Online and Microsoft Dynamics 365 Sales .
Object compatibility
1 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
PlanPlus Online: Not publicly documented.
Data volume sensitivity
PlanPlus Online 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 PlanPlus Online to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your PlanPlus Online 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 PlanPlus Online
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.