CRM migration

Migrate from PlanPlus Online to Microsoft Dynamics 365 Sales

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 logo

PlanPlus Online

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

75%

6 of 8

objects map 1:1 between PlanPlus Online and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

PlanPlus Online logo

PlanPlus Online

What's pushing teams away

  • Lack of a public API makes automated migrations and third-party integrations difficult, forcing manual export work.
  • Mobile apps are separate from the web platform and require careful sync setup, causing frustration when calendars diverge.
  • Business Edition pricing at $199.99/month for the tier plus per-user costs scales poorly for growing sales teams.
  • Custom field and workflow customization is limited compared to mainstream CRMs, restricting advanced automation.
  • Integration ecosystem is narrow—users report difficulty connecting PlanPlus Online data to modern BI or marketing automation tools.

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 PlanPlus Online objects map to Microsoft Dynamics 365 Sales

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

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

PlanPlus 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

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

PlanPlus 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)

maps to

Microsoft Dynamics 365 Sales

Opportunity

1:1
Fully supported

PlanPlus 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

maps to

Microsoft Dynamics 365 Sales

Appointment (Activity)

1:1
Fully supported

Calendar 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

maps to

Microsoft Dynamics 365 Sales

Task

1:1
Fully supported

Tasks 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

maps to

Microsoft Dynamics 365 Sales

Project (Custom) or Task

lossy
Fully supported

PlanPlus 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

maps to

Microsoft Dynamics 365 Sales

Custom Field

lossy
Fully supported

Custom 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

maps to

Microsoft Dynamics 365 Sales

User

1:1
Fully supported

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

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.

PlanPlus Online logo

PlanPlus Online gotchas

High

No public API means no automated migration pipeline

High

Data export blocked for delinquent accounts

Medium

Planner Edition lacks sync and export infrastructure

Medium

Auto-renewal with annual price adjustment

Low

Time zone settings must be correct before sync setup

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

  • PlanPlus Online has no public API; all migration uses manual CSV exports

    PlanPlus Online does not publish a REST API for programmatic data access. All migration data must be extracted via the web interface's CSV export feature and data dumps from sync connectors. We download each object type separately and assemble the migration dataset manually. This extends migration timelines because we cannot perform incremental delta syncs between the source and destination. We recommend scheduling two to three weeks of manual export work before the migration window opens. If the PlanPlus Online account is delinquent on payments, data export may be restricted until the balance is cleared, which is a hard blocker we verify during scoping.

  • Deal stage names require explicit mapping between platforms

    PlanPlus Online's pipeline stage vocabulary does not align with Microsoft Dynamics 365 Sales ' default StageName picklist. We create an explicit stage mapping table during scoping that pairs each PlanPlus Online stage name to a Microsoft Dynamics 365 Sales Process and StageName value. If PlanPlus Online uses custom stage names reflecting a Franklin Covey or sales methodology, those labels do not map automatically and require the customer's input to assign the correct Dynamics 365 equivalent. Closed-won and closed-lost reasons in PlanPlus Online map to custom Opportunity fields in Dynamics 365 since the destination does not have an equivalent built-in loss-reason field.

  • Planner Edition lacks sync and export infrastructure

    PlanPlus Online Planner Edition ($69.99/year) is a personal productivity tool without the sync connections or team features of Essentials, Professional, and Business editions. It does not have the same export infrastructure as paid editions. If the migration includes Planner Edition accounts, we treat them as personal task-and-calendar exports only, migrating them to the individual's personal account in Dynamics 365 rather than as team CRM data. The customer's admin must decide whether to provision Planner users as Dynamics 365 User records or consolidate their data into existing User accounts.

  • Sync connections and calendar integrations do not carry over

    Sync connections to Google, Microsoft 365, and Outlook are authentication configurations stored in PlanPlus Online that do not export or carry over to Dynamics 365. Calendar events and tasks that were synced from external calendars are migrated as static data, but the active sync relationships are severed. We document which external systems were connected so the customer can reconfigure the equivalent Dynamics 365 Outlook integration or Microsoft 365 connector post-migration. Time zone settings in PlanPlus Online must be verified before export; mismatches cause calendar events to shift by the offset during migration.

  • Custom fields may require pre-migration transformation

    PlanPlus Online custom fields export as flat key-value pairs without type metadata, which means the destination field type must be inferred from the data content. Text-heavy custom fields with mixed formats may need a pre-migration transformation step to standardize them into consistent Dynamics 365 field types. We run a data quality audit on the exported CSV before import and flag any custom fields that contain ambiguous data (e.g., a field containing both dates and text). Fields that cannot be safely typed are flagged for manual review and may need to be stored as text in Dynamics 365 with a manual reclassification step post-migration.

Migration approach

Six steps for a successful PlanPlus Online to Microsoft Dynamics 365 Sales data migration

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

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

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

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

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

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

Context on both ends of the pair

PlanPlus Online logo

PlanPlus Online

Source

Strengths

  • Franklin Covey methodology alignment gives it a structured planning philosophy competitors lack.
  • Sync connectors to Google and Microsoft 365 keep calendar data current without manual re-entry.
  • Group calendaring with drag-and-drop task scheduling is intuitive for busy professionals.
  • Single-platform pricing covers CRM, project tracking, and calendar tools.
  • Lowest pricing tier at $157.95/year is accessible for individual users.

Weaknesses

  • No public API documented means all migration relies on manual CSV exports.
  • Limited third-party integrations compared to mainstream CRM platforms.
  • Sync setup is complex—time zone mismatches between devices cause calendar drift.
  • Business Edition pricing at $199.99 plus per-user costs is expensive relative to market.
  • Custom field and workflow automation capabilities lag behind Salesforce, HubSpot, and Zoho.
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. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

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

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • 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

    PlanPlus Online: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your PlanPlus Online 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 PlanPlus Online to Microsoft Dynamics 365 Sales data migrations

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

Can't find your answer?

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 consultation

Most migrations land between three and five weeks for accounts under 10,000 Contacts and 2,000 Deals from a single PlanPlus Online edition with clean export data. Migrations with multi-edition sources (Planner Edition personal exports requiring separation from team CRM data), large historical calendars (over 100,000 activity records), or complex custom field schemas requiring pre-migration transformation move to eight to fourteen weeks. The lack of a PlanPlus Online API means the manual CSV export phase adds two to three weeks of preparation time before the migration window opens, regardless of which Dynamics 365 edition is the destination.

Adjacent paths

Related migrations to explore

Ready when you are

Move from PlanPlus Online.
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