Migrate your Myprosperity data
White-labelled client wealth portal for Australian accounting and financial advisory practices. Clients get a branded mobile app and portal; the practice gets a client-facing hub that sits alongside their back-office CRM.
In its favor
Why people choose Myprosperity
The signal that keeps Myprosperity on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Whole-of-wealth client portal automates data collection across banks, property, vehicles, planning, and investment platforms via live feeds — eliminating manual fact-find for financial advisors.
Household grouping lets family members be added as account owners with full feature access, fitting multi-generational financial planning use cases.
Automated wealth reports stay current via live feeds without advisor manual refresh — material time savings for review meetings.
Goal-tracking features link directly to underlying accounts (debt-reduction to loan accounts, retirement to balance sheets) for live progress visibility.
Won 2019 and 2020 Finnies Excellence in Wealth Management Award, reinforcing market credibility in the Australian financial-advisory space.
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.
Reasons to switch
Why people leave Myprosperity
The recurring reasons buyers give for replacing Myprosperity. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Myprosperity fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Myprosperity pricing overview
Myprosperity charges per-client subscription on top of a Practice Partner plan. The Starter subscription is free within Partner plans; the Pro subscription costs $14.95 per client per month. Partner plans themselves are priced by firm size and client volume (300–2,000 Starter clients, 5–100 Pro clients) — pricing is not publicly listed and requires a sales inquiry.
Starter
Tier 1 of 5
Free (included in all Partner plans)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Myprosperity's schedule — see our quote-based pricing →
What gets migrated
Myprosperity object support
Object-by-object support for Myprosperity migrations. Per-pair details surface during scoping.
Clients
Fully supportedThe primary person record in Myprosperity. Contains name, contact details, date of birth, and lifecycle stage. We map Client records 1:1 and preserve the client-facing portal access status.
Relationships
Mapping requiredNamed links between a Client and an advisor, accountant, or family member. The API exposes a Relationship field with coded values (Owner=0, Accountant=1, Lawyer=2, etc.). We translate these to the destination's role field and flag any unmapped relationship types.
Practice
Mapping requiredThe accounting or advisory firm record. Contains staff licenses, branding settings, and tier configuration. We preserve the Practice name and subdomain and map staff user assignments to the destination's user list.
Bank Accounts
Mapping requiredConnected bank and credit card accounts with transaction feeds. Bank feed data is typically 90 days of history for Starter clients and live-synced for Pro clients. We flag feed vintage at export time so the destination reflects what was actually available.
Investment Accounts
Mapping requiredLinked investment account holdings sourced via XPLAN, Macquarie, and other feed integrations. We export current holdings, account values, and ticker-level positions where available from the API.
Property Holdings
Mapping requiredProperty valuations (residential, commercial, land) attached to a Client. Valuation frequency depends on tier — one-time for Starter, monthly for Pro. We preserve the last valuation date and value so the destination can display a current snapshot.
Motor Vehicles
Mapping requiredVehicle records with make, model, year, and valuation. Same tier-gated frequency rules as Property — one-time for Starter, monthly for Pro.
Documents
Mapping requiredFiles uploaded to a Client's portal, including statements, reports, and eSignature packages. We export document metadata, binary blobs, and eSignature status. Storage is tier-limited (50–200GB), so we flag any clients near their document quota.
Fact Finds
Mapping requiredCustomised fact-find questionnaires completed by clients. Only available on Partner 3 and Partner 4 tiers. We export question text and client answers as a structured object.
Surveys
Mapping requiredClient survey responses and analytics. Advanced analytics on survey responses are tier-gated to Partner 3 and 4. We export response data and flag whether advanced analytics were available in the source tier.
Wealth Snapshots
Mapping requiredAggregated net-worth and asset allocation summaries generated monthly for Pro clients. Starter clients receive one-time snapshots. We preserve the most recent snapshot and flag the generation date.
Tasks / To-Dos
Mapping requiredInternal tasks and reminders created by practice staff for a client or for themselves. We export task text, due dates, assignee, and completion status.
Custom Fields
Mapping requiredCustom properties on Client records. Availability depends on tier. We export all populated custom fields and their current values at migration time.
Cashflow Records
Mapping requiredMonthly income and expense records tied to a Client. Pro clients get live cashflow data; Starter clients get one-time snapshots. We export the most recent period's cashflow breakdown.
| Object | Support | Notes |
|---|---|---|
| Clients | Fully supported | The primary person record in Myprosperity. Contains name, contact details, date of birth, and lifecycle stage. We map Client records 1:1 and preserve the client-facing portal access status. |
| Relationships | Mapping required | Named links between a Client and an advisor, accountant, or family member. The API exposes a Relationship field with coded values (Owner=0, Accountant=1, Lawyer=2, etc.). We translate these to the destination's role field and flag any unmapped relationship types. |
| Practice | Mapping required | The accounting or advisory firm record. Contains staff licenses, branding settings, and tier configuration. We preserve the Practice name and subdomain and map staff user assignments to the destination's user list. |
| Bank Accounts | Mapping required | Connected bank and credit card accounts with transaction feeds. Bank feed data is typically 90 days of history for Starter clients and live-synced for Pro clients. We flag feed vintage at export time so the destination reflects what was actually available. |
| Investment Accounts | Mapping required | Linked investment account holdings sourced via XPLAN, Macquarie, and other feed integrations. We export current holdings, account values, and ticker-level positions where available from the API. |
| Property Holdings | Mapping required | Property valuations (residential, commercial, land) attached to a Client. Valuation frequency depends on tier — one-time for Starter, monthly for Pro. We preserve the last valuation date and value so the destination can display a current snapshot. |
| Motor Vehicles | Mapping required | Vehicle records with make, model, year, and valuation. Same tier-gated frequency rules as Property — one-time for Starter, monthly for Pro. |
| Documents | Mapping required | Files uploaded to a Client's portal, including statements, reports, and eSignature packages. We export document metadata, binary blobs, and eSignature status. Storage is tier-limited (50–200GB), so we flag any clients near their document quota. |
| Fact Finds | Mapping required | Customised fact-find questionnaires completed by clients. Only available on Partner 3 and Partner 4 tiers. We export question text and client answers as a structured object. |
| Surveys | Mapping required | Client survey responses and analytics. Advanced analytics on survey responses are tier-gated to Partner 3 and 4. We export response data and flag whether advanced analytics were available in the source tier. |
| Wealth Snapshots | Mapping required | Aggregated net-worth and asset allocation summaries generated monthly for Pro clients. Starter clients receive one-time snapshots. We preserve the most recent snapshot and flag the generation date. |
| Tasks / To-Dos | Mapping required | Internal tasks and reminders created by practice staff for a client or for themselves. We export task text, due dates, assignee, and completion status. |
| Custom Fields | Mapping required | Custom properties on Client records. Availability depends on tier. We export all populated custom fields and their current values at migration time. |
| Cashflow Records | Mapping required | Monthly income and expense records tied to a Client. Pro clients get live cashflow data; Starter clients get one-time snapshots. We export the most recent period's cashflow breakdown. |
Gotchas
What to watch for in Myprosperity migrations
Issues we've hit on past Myprosperity migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No bulk data export endpoint requires iterative API polling
Tier determines data vintage, not just feature availability
Document storage caps can silently block large migrations
Client Relationship roles have a hard-coded integer schema
eSignature packages are stored as stateful workflow objects, not plain documents
| Severity | Issue |
|---|---|
| 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 |
Leaving Myprosperity?
Where Myprosperity customers move next
12 destinations Myprosperity can migrate to.
How a Myprosperity migration works
Four steps, Myprosperity-specific
Connect
OAuth 2.0 and API key (documented at api.myprosperity.com.au/help/index) into Myprosperity. Scopes limited to read-only on the data we move.
Map
We translate Myprosperity-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Myprosperity quirks before production.
Migrate
Full migration with Myprosperity rate-limit handling. Rollback available throughout.
FAQ
Myprosperity migration FAQ
Answers to the questions buyers ask most during Myprosperity migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Myprosperity migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Myprosperity.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Myprosperity setup and destination — written quote back within a business day.