How long does a Myprosperity to Dynamics 365 Sales migration take?

Most Myprosperity to Dynamics 365 Sales migrations complete within 3–5 business days of clock time for under 10,000 client portal records. The extraction phase is constrained by Myprosperity's API rate limits — large client databases may need additional batch windows that extend the timeline. Custom Dataverse table creation (for property valuations) and SharePoint document re-upload add 1–2 days to the overall schedule. Complex setups with 50,000+ records or multiple custom financial data fields typically require 10–20 business days.

Will my Myprosperity workflows and automations migrate to Dynamics 365 Sales?

No. Myprosperity client task reminders, document request workflows, email notifications, and portal event automations do not migrate as configuration — they have no equivalent structure in Dynamics 365 Sales. They must be rebuilt using Power Automate or Dynamics 365 business process flows after the data migration completes. FlitStack AI exports a structured JSON reference of every active Myprosperity workflow definition so your Dynamics administrator has a complete rebuild specification. Budget separately for post-migration Power Automate configuration work.

What does a Myprosperity client relationship type become in Dynamics 365 Sales?

Myprosperity stores adviser-client relationships as integer codes (0=Owner, 1=Accountant, 2=Lawyer, 3=Wife, 4=Husband, 5=Child). Dynamics 365 Sales has no native relationship-type field on Contact — we create a custom pick-list field called RelationshipType__c and map each integer code to its human-readable label. The relationship label is preserved on the Contact record and can be used in Dynamics views, reports, and Power Automate triggers. If your practice uses additional custom relationship categories beyond these six codes, we extend the pick-list accordingly during schema setup.

Can I migrate Myprosperity financial data (balances, valuations) to Dynamics 365 Sales?

Yes, but it requires custom fields in Dynamics 365 Sales since no native equivalent exists. Bank account balances, investment portfolio values, and superannuation balances from Myprosperity are mapped to custom Decimal fields on Account: AccountBalance__c, PortfolioValue__c, and CashHoldings__c. Property and vehicle valuations are stored in a custom PropertyValuation__c Dataverse table with a lookup to Account. If your Dynamics licence is Sales Professional, be aware of the 15 custom table limit — Enterprise or Premium removes this ceiling.

What happens to Myprosperity documents and attachments during the migration?

Myprosperity documents (statements, valuations, signed contracts) are downloaded from the portal API and re-uploaded to Dynamics 365 as Notes attachments on the parent Contact or Account record. For large document libraries, we use Dynamics 365's native SharePoint integration — documents are uploaded to the associated SharePoint document library and linked via the entity's document location record. Myprosperity's document metadata (type, date, owner) is preserved in the Dynamics Annotation record.

Does the migration affect my Myprosperity account during cutover?

No. FlitStack AI uses scoped read access on Myprosperity via the REST API — your team can continue using the Myprosperity portal throughout the migration. A delta-pickup window (typically 24–48 hours) runs after the full migration to capture any records created or modified in Myprosperity during the cutover period. These delta records are inserted into Dynamics 365 before go-live so the destination system reflects the final state of Myprosperity at the moment of switchover.

My Myprosperity subscription is on a tier with client count limits — how does that affect migration pricing?

Your Myprosperity subscription tier (Starter: 300–2,000 clients; Pro: 5–100 included, then $14.95 per additional client) affects the number of source records we migrate, not the destination. FlitStack AI migration pricing scales with the record count we extract from Myprosperity. The Dynamics 365 side has no per-client billing model — you can migrate all historical Myprosperity clients regardless of your current subscription tier. If your tier limits how many active clients you can have simultaneously, we coordinate the migration to stay within limits during extraction.

What custom schema must be created in Dynamics 365 before the migration runs?

We create the following before migration: RelationshipType__c pick-list on Contact (six values for Owner, Accountant, Lawyer, Wife, Husband, Child); AccountBalance__c, PortfolioValue__c, CashHoldings__c, and Custom_ABN__c custom fields on Account; and the PropertyValuation__c custom Dataverse table with fields for PropertyType__c, PropertyAddress__c, ValuationAmount__c, ValuationDate__c, and an AccountId lookup. If your Dynamics licence is Sales Professional, we flag the custom table count upfront so you can upgrade to Enterprise if needed before schema setup begins.

Myprosperity to Microsoft Dynamics 365 Sales Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Myprosperity is a client-facing wealth portal platform built for financial advisers and accounting practices — it stores client portal users, relationship types (Owner, Accountant, Lawyer, Wife, Husband, Child), financial account balances, portfolio valuations, property valuations, and document attachments behind a white-labelled client portal. Dynamics 365 Sales is a Microsoft CRM built on Dataverse that stores contacts, accounts, opportunities, and custom tables. The two platforms share almost no schema overlap: Myprosperity has no native contact-company association model and stores financial data in portal-specific properties, while Dynamics 365 Sales uses Account as the primary organizational record with Contact linked via a lookup and financial fields requiring custom fields on Account or custom Dataverse tables. We migrate Myprosperity User records as Dynamics 365 Contacts, Myprosperity Client records as Dynamics 365 Accounts, relationship types as a custom pick-list field on Contact (since Dynamics has no native relationship-type concept), financial balances and portfolio values as custom fields on Account, property valuations as a custom Dataverse table, and documents as Notes attachments on the parent Contact or Account. Document files from Myprosperity's portal storage are downloaded and re-uploaded to Dynamics 365's native SharePoint integration or as file attachments. Workflows, automations, and client-portal configurations do not migrate — those are rebuilt using Power Automate or Dynamics 365 business process flows post-migration.

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

Myprosperity

What's pushing teams away

Primary market is Australia (myprosperity.com.au with a UK arm); advisors and firms in North America have limited local data-feed coverage and support.
Pricing is not publicly published — sales-led model slows procurement for firms used to transparent SaaS tiers.
Heavy reliance on bank/investment data feeds means feature value drops sharply when an Australian institution discontinues feed support.
Power users requesting deep customisation beyond standard wealth views and goal types may need third-party planning tools alongside myprosperity.
Property and investment data quality depends on third-party providers — outages or stale feed updates surface as client-facing issues.

Choosing

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

Each row shows how a Myprosperity 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.

Myprosperity

User

maps to

Microsoft Dynamics 365 Sales

Contact

1:1

Fully supported

Myprosperity User maps directly to Dynamics 365 Contact. Each portal user becomes a Contact record. The user's primary Client association maps via AccountId lookup — the Client must be migrated first so the Contact.AccountId foreign key resolves correctly at insert time.

Myprosperity

Client

maps to

Microsoft Dynamics 365 Sales

Account

1:1

Fully supported

Myprosperity Client maps to Dynamics 365 Account. The Client represents the household or individual entity — in Dynamics this maps to Account (individual accounts use the 'Individual' account type). ABN/ACN and business name map to Account.Industry or custom fields depending on entity type.

Myprosperity

Relationship

maps to

Microsoft Dynamics 365 Sales

Contact (custom pick-list field)

1:1

Fully supported

Myprosperity relationship type (integer code: 0=Owner, 1=Accountant, 2=Lawyer, 3=Wife, 4=Husband, 5=Child) has no native equivalent in Dynamics 365 Sales. We map the integer to a custom pick-list field RelationshipType__c on Contact, preserving the exact label semantics so advisers can filter by relationship in Dynamics views and reports.

Myprosperity

FinancialAccount (balance, portfolio value, cash holdings)

maps to

Microsoft Dynamics 365 Sales

Account (custom fields)

1:1

Fully supported

Myprosperity financial account data — bank balances, investment portfolio values, superannuation balances — are stored as portal properties. Dynamics 365 Sales has no native financial-balance fields. We create custom Decimal fields on Account (e.g., AccountBalance__c, PortfolioValue__c, CashHoldings__c) and map values directly from the Myprosperity financial data export.

Myprosperity

Property (residential, investment, vehicle valuations)

maps to

Microsoft Dynamics 365 Sales

Custom Dataverse Table: PropertyValuation

1:1

Fully supported

Myprosperity property and vehicle valuation records have no direct Dynamics 365 Sales equivalent — Opportunity and Account do not natively store asset valuations. We create a custom PropertyValuation Dataverse table with fields for property type, address, valuation amount, valuation date, and source (Owner, Accountant, etc.), linked to Account via a lookup relationship.

Myprosperity

Document (statements, contracts, valuations)

maps to

Microsoft Dynamics 365 Sales

Contact/Account Notes and Attachments / SharePoint

1:1

Fully supported

Myprosperity documents are downloaded from the portal API and re-uploaded as Notes attachments on the parent Contact or Account record in Dynamics 365. For large document volumes we use Dynamics 365's SharePoint integration — documents are uploaded to the associated SharePoint document library and linked via the entity's document location record.

Myprosperity

User.email (owner/adviser lookup)

maps to

Microsoft Dynamics 365 Sales

SystemUser / Contact.OwnerId

1:1

Fully supported

Myprosperity does not have a native owner field on User. Adviser-assigned users are resolved by email match against Dynamics 365 SystemUser records. Unmatched users are flagged before migration — the practice either creates the user in Dynamics first or assigns a fallback owner (e.g., the practice principal) for the Contact record.

Myprosperity

Client.createdate / User.createdate

maps to

Microsoft Dynamics 365 Sales

Contact.OriginalCreateDate__c (custom datetime)

1:1

Fully supported

Dynamics 365 sets CreatedDate at insert time — the original Myprosperity create timestamp is lost unless preserved explicitly. We create a custom datetime field OriginalCreateDate__c on Contact and populate it from the Myprosperity createdate value so historical reporting continuity is maintained in Dynamics.

Myprosperity

Myprosperity custom client properties

maps to

Microsoft Dynamics 365 Sales

Account (custom fields) / Dataverse custom tables

1:1

Fully supported

Myprosperity allows practice-specific custom properties on client profiles. These map to custom fields on Account using the property name as the field label and the __c suffix in the API name. Complex multi-value custom properties (e.g., lists of related entities) may require a custom Dataverse table with a lookup to Account.

Myprosperity

Myprosperity subscription tier / client limit

maps to

Microsoft Dynamics 365 Sales

N/A — informational only

1:1

Fully supported

Myprosperity's tier model (Starter limits: 300–2,000 client subscriptions; Pro: 5–100 included, then $14.95/client) has no Dynamics 365 equivalent. We document the tier and record count for migration scoping but do not create a corresponding object — Dynamics 365 Sales has no per-client billing model.

Myprosperity	Microsoft Dynamics 365 Sales	Compatibility
User	Contact1:1	Fully supported
Client	Account1:1	Fully supported
Relationship	Contact (custom pick-list field)1:1	Fully supported
FinancialAccount (balance, portfolio value, cash holdings)	Account (custom fields)1:1	Fully supported
Property (residential, investment, vehicle valuations)	Custom Dataverse Table: PropertyValuation1:1	Fully supported
Document (statements, contracts, valuations)	Contact/Account Notes and Attachments / SharePoint1:1	Fully supported
User.email (owner/adviser lookup)	SystemUser / Contact.OwnerId1:1	Fully supported
Client.createdate / User.createdate	Contact.OriginalCreateDate__c (custom datetime)1:1	Fully supported
Myprosperity custom client properties	Account (custom fields) / Dataverse custom tables1:1	Fully supported
Myprosperity subscription tier / client limit	N/A — informational only1:1	Fully supported

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.

Myprosperity gotchas

High

No bulk data export endpoint requires iterative API polling

High

Tier determines data vintage, not just feature availability

Medium

Document storage caps can silently block large migrations

Medium

Client Relationship roles have a hard-coded integer schema

Medium

eSignature packages are stored as stateful workflow objects, not plain documents

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

Myprosperity gotchas		Microsoft Dynamics 365 Sales gotchas
Severity	Issue	Severity	Issue
High	No bulk data export endpoint requires iterative API polling	High	Professional tier 15-table custom table limit blocks migrations
High	Tier determines data vintage, not just feature availability	High	October 2024 pricing increase applies at renewal for all customers
Medium	Document storage caps can silently block large migrations	Medium	Custom fields must be created in the UI before API writes
Medium	Client Relationship roles have a hard-coded integer schema	Medium	Power Platform request limits apply to bulk migrations
Medium	eSignature packages are stored as stateful workflow objects, not plain documents	Medium	Activity records orphaned to inactive owners fail silently

Pair-specific challenges

Myprosperity relationship type integer codes require value-mapping to a custom pick-list

Myprosperity stores adviser-client relationships as integer codes (0=Owner, 1=Accountant, 2=Lawyer, 3=Wife, 4=Husband, 5=Child). Dynamics 365 Sales has no native relationship-type field on Contact — there is no built-in pick-list, taxonomy, or customisable relationship label. If this data is business-critical, FlitStack AI creates a RelationshipType__c custom pick-list field on Contact and maps each integer code to its matching human-readable label. If the mapping is skipped, the integer value is stored as a number field and advisers lose the relationship context in Dynamics reports and views.
Myprosperity financial data (balances, valuations) requires custom Dataverse fields and tables

Dynamics 365 Sales does not have native fields for bank account balances, investment portfolio values, superannuation balances, or property/vehicle valuations. These data points exist natively in Myprosperity client profiles but have no standard Dynamics 365 equivalent. We handle this by creating custom Decimal fields on Account (AccountBalance__c, PortfolioValue__c, CashHoldings__c) and a custom PropertyValuation__c Dataverse table linked to Account for multi-property households. If your Dynamics 365 licence is Sales Professional, note the 15-table customisation limit — Enterprise or Premium removes this ceiling.
Myprosperity API rate limits may throttle large-volume exports

The Myprosperity REST API (api.myprosperity.com.au) applies rate limits on data exports. For large client databases (10,000+ portal users), export requests may be throttled or return 429 Too Many Requests responses, extending the extraction phase. FlitStack AI implements exponential backoff and respects Retry-After headers during extraction. We recommend coordinating with your Myprosperity account manager to confirm API allocation tiers before migration scoping — higher-tier subscriptions may carry increased API rate limits.
Client portal files require download-and-reupload — no direct storage migration

Myprosperity stores client documents (statements, valuations, signed contracts, policy documents) in its own portal storage. There is no bulk-export storage migration path — files must be downloaded via the API and re-uploaded to Dynamics 365. Large document libraries (thousands of files) are re-uploaded using Dynamics 365's SharePoint integration. If your Myprosperity subscription includes premium document storage tiers, the file-size limits on Dynamics 365 SharePoint (default 10MB per file, configurable up to 2GB) must be verified before migration begins.
Myprosperity workflows, portal automations, and task rules do not migrate

Myprosperity automations — client task reminders, document request workflows, email notifications triggered by portal events — have no equivalent in Dynamics 365 Sales and cannot be migrated as configuration. They must be rebuilt in Dynamics 365 using Power Automate flows or Dynamics business process flows after the data migration is complete. FlitStack AI exports a structured JSON reference of all active Myprosperity workflow definitions so your Dynamics administrator can use it as a rebuild specification. This is disclosed upfront so the practice can budget for post-migration Power Automate configuration work.

Migration approach

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

Assess Myprosperity API and export the schema

FlitStack AI connects to the Myprosperity REST API and inventories all User, Client, FinancialAccount, Property, and Document records. We pull the field schema to identify custom properties, relationship type distributions, and financial data fields present in your account. API rate limits are tested against a sample export to calibrate extraction timing. We also inventory active Myprosperity workflows and automations for the rebuild reference document.
Stand up Dynamics 365 schema: custom fields and Dataverse tables

Before data lands in Dynamics 365, we create the required custom schema based on the Myprosperity field inventory: RelationshipType__c pick-list on Contact; AccountBalance__c, PortfolioValue__c, CashHoldings__c, and Custom_ABN__c fields on Account; and the PropertyValuation__c custom Dataverse table with its lookup to Account. We verify the field API names and data types against your Dynamics environment before extraction begins. If your licence is Sales Professional, we flag the custom-table count to ensure you stay within the 15-table limit.
Extract, transform, and validate with a field-level diff

Myprosperity data is extracted via the REST API in batches, respecting rate limits. Each record is transformed according to the field mapping: integer relationship codes become RelationshipType__c pick-list labels, financial values are cast to Decimal, and property records are upserted to the PropertyValuation__c custom table. A sample migration (typically 100–500 records) is run first against a Dynamics 365 sandbox environment, and FlitStack AI generates a field-level diff report showing source value versus destination field for every mapped property so you can verify accuracy before the full run.
Cut over with delta-pickup window and audit log

The full migration runs against your live Dynamics 365 environment. A delta-pickup window (typically 24–48 hours after the full run) captures any Myprosperity records created or modified during the cutover period. Every insert, update, and error is written to a migration audit log. If reconciliation fails, one-click rollback reverts the Dynamics environment to its pre-migration state. Documents are uploaded in parallel to SharePoint or as entity attachments, with the parent Contact or Account linked via ObjectId.
Deliver the rebuild reference and post-migration handoff

FlitStack AI delivers the exported workflow JSON (for Power Automate rebuild), the complete field-mapping manifest, and the migration audit log as part of the handoff package. We schedule a 30-minute post-migration call with your Dynamics administrator to walk through the mapping decisions, review any records that require manual review, and confirm the next steps for rebuilding Myprosperity automations in Power Automate.

Platform deep dives

Context on both ends of the pair

Myprosperity

Source

Strengths

Client portal with white-labelled mobile app builds brand visibility for accounting and advisory practices
Integrates with Xplan, Xero Practice Manager, and MYOB for practice-side data import
Investment feed aggregation from XPLAN and Macquarie consolidates client wealth data in one view
Document e-signing via Annature integrates into the client workflow natively
Pro tier provides live bank feed syncing and monthly valuation updates

Weaknesses

No publicly documented bulk export or migration API — data extraction relies on per-record API calls or CSV/XPM import templates
Starter tier limits bank feeds to one-time sync and valuations to one-time snapshots, reducing the richness of migrated financial history
Tier-gated features (Fact Finds, Survey Analytics, Advanced Mobile Branding) mean not all clients on a plan have equivalent data
Document storage caps (50–200GB) may require archival or selective migration for high-volume practices
Practice Portal staff licenses and client subscription limits are tied to the current tier — over-importing will trigger an upgrade

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

	Myprosperity Source	Microsoft Dynamics 365 Sales Destination
Strengths	Client portal with white-labelled mobile app builds brand visibility for accounting and advisory practices Integrates with Xplan, Xero Practice Manager, and MYOB for practice-side data import Investment feed aggregation from XPLAN and Macquarie consolidates client wealth data in one view Document e-signing via Annature integrates into the client workflow natively Pro tier provides live bank feed syncing and monthly valuation updates	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	No publicly documented bulk export or migration API — data extraction relies on per-record API calls or CSV/XPM import templates Starter tier limits bank feeds to one-time sync and valuations to one-time snapshots, reducing the richness of migrated financial history Tier-gated features (Fact Finds, Survey Analytics, Advanced Mobile Branding) mean not all clients on a plan have equivalent data Document storage caps (50–200GB) may require archival or selective migration for high-volume practices Practice Portal staff licenses and client subscription limits are tied to the current tier — over-importing will trigger an upgrade	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

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Myprosperity to Microsoft Dynamics 365 Sales

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Myprosperity

Microsoft Dynamics 365 Sales

How Myprosperity objects map to Microsoft Dynamics 365 Sales

What specifically takes care here

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

Context on both ends of the pair

How hard is this migration?

Estimate your Myprosperity to Microsoft Dynamics 365 Sales migration cost

What are you migrating?

Frequently asked questions about Myprosperity to Microsoft Dynamics 365 Sales data migrations

Can't find your answer?

Related migrations to explore

Move from Myprosperity.
Land in Microsoft Dynamics 365 Sales , intact.

Migrate from Myprosperity to Microsoft Dynamics 365 Sales

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Myprosperity

Microsoft Dynamics 365 Sales

How Myprosperity objects map to Microsoft Dynamics 365 Sales

What specifically takes care here

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

Context on both ends of the pair

How hard is this migration?

Estimate your Myprosperity to Microsoft Dynamics 365 Sales migration cost

Frequently asked questions about Myprosperity to Microsoft Dynamics 365 Sales data migrations

Can't find your answer?

How long does a Myprosperity to Dynamics 365 Sales migration take?

Will my Myprosperity workflows and automations migrate to Dynamics 365 Sales?

What does a Myprosperity client relationship type become in Dynamics 365 Sales?

Can I migrate Myprosperity financial data (balances, valuations) to Dynamics 365 Sales?

What happens to Myprosperity documents and attachments during the migration?

Does the migration affect my Myprosperity account during cutover?

My Myprosperity subscription is on a tier with client count limits — how does that affect migration pricing?

What custom schema must be created in Dynamics 365 before the migration runs?

Related migrations to explore

Move from Myprosperity. Land in Microsoft Dynamics 365 Sales , intact.

Move from Myprosperity.
Land in Microsoft Dynamics 365 Sales , intact.