CRM migration

Migrate from Myprosperity to Freshsales

Field-level mapping, validation, and rollback between Myprosperity and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.

Myprosperity logo

Myprosperity

Source

Freshsales

Destination

Freshsales logo

Compatibility

92%

11 of 12

objects map 1:1 between Myprosperity and Freshsales.

Complexity

BStandard

Timeline

3–7 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

MyProsperity is a white-labeled client wealth portal built for Australian accountants and financial advisers — its data model centers on Users (clients), Relationships, Documents, and financial properties like assets and valuations. Freshsales is a sales CRM with Leads, Contacts, Accounts, Opportunities (Deals), and Activities, backed by Freddy AI for lead scoring and deal insights. The migration carries every MyProsperity user record into Freshsales Contacts, every relationship into custom pick-list fields or Contact Role links, and every financial property into custom fields on the Contact or Account object. Document metadata migrates as custom fields or notes; the actual files re-upload to Freshsales Files. Freshsales Workflows, Sales Sequences, and lead-routing rules must be rebuilt from scratch using Freshsales' Admin Settings workflow builder. The migration runs via Freshsales REST API (rate-limited per plan: Growth 1,000 req/hr, Pro 2,000 req/hr, Enterprise 5,000 req/hr) with scoped read access on MyProsperity and a 24–48 hour delta-pickup window capturing in-flight changes at cutover.

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 logo

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

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How Myprosperity objects map to Freshsales

Each row shows how a Myprosperity object lands in Freshsales, 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

Freshsales

Contact

1:1
Fully supported

MyProsperity Users map directly to Freshsales Contacts. The email address is the primary key for de-duplication and owner resolution. Users without an email address are flagged for manual review before migration — Freshsales requires a valid email for Contact creation via API.

Myprosperity

User

maps to

Freshsales

Lead

1:many
Fully supported

MyProsperity Users with a relationship_type of 'Lead' or 'Prospect' route to Freshsales Lead. All other relationship types (Owner, Family, Accountant) route to Contact. The split is determined by a pre-migration relationship_type audit against MyProsperity's API field values. If any User lacks a relationship_type value, it defaults to Contact and is flagged for review.

Myprosperity

Relationship

maps to

Freshsales

Contact Role / Custom Pick-list Field

1:1
Fully supported

MyProsperity Relationship records define how a User relates to a client (Owner=0, Accountant=1, Lawyer=2, Wife=3, Husband=4, Child=5). These map to Freshsales custom pick-list field Relationship_Type__c on Contact. For adviser-to-client relationships, Freshsales Contact Roles provide the built-in equivalent. The integer codes are preserved in a hidden reference field for audit and de‑duplication.

Myprosperity

Document

maps to

Freshsales

Note / Freshsales Files

1:1
Fully supported

MyProsperity Documents (attached statements, signed forms, valuations) migrate as Freshsales Notes with the original filename stored in the Note title. If the file is binary, it re-uploads to Freshsales Files. Document create timestamps and associated User links are preserved as Note metadata fields.

Myprosperity

Financial Property (asset, valuation)

maps to

Freshsales

Custom Object: Financial_Asset__c

1:1
Fully supported

MyProsperity financial properties — property valuations, investment balances, insurance policies — have no Freshsales native equivalent. We create a Financial_Asset__c custom object with fields for asset type, value, currency, and a lookup to the Contact. N:1 relationship from asset to contact preserves the client-centric model.

Myprosperity

Practice Portal Staff User

maps to

Freshsales

Freshsales User

1:1
Fully supported

MyProsperity Practice Portal staff licences ( Adviser, Paraplanner, Admin) map to Freshsales Users. Owner resolution uses email match — if the MyProsperity staff email matches a Freshsales user, the Contact OwnerId links automatically. Unmatched staff are flagged for Freshsales admin to invite before migration.

Myprosperity

Investment Feed

maps to

Freshsales

Custom Field on Contact / Account

1:1
Fully supported

MyProsperity live investment feeds (Xplan, Macquarie) pull portfolio data into the portal. These values cannot be exported as a data feed from MyProsperity. We preserve the last-synced snapshot values as custom fields on the Contact (Last_Portfolio_Value__c, Last_Sync_Date__c) — ongoing sync requires a Freshworks or Zapier integration rebuild.

Myprosperity

Client Subscription Tier

maps to

Freshsales

Custom Field on Contact

1:1
Fully supported

MyProsperity subscription tiers (Starter, Pro, Mobile First) map to a custom pick-list field Client_Tier__c on Contact. The mapping is 1:1 — Starter maps to Starter, Pro to Pro, Mobile First to Mobile First. Subscription renewal dates migrate as a custom date field.

Myprosperity

Balance Sheet / Cashflow Report

maps to

Freshsales

Custom Field on Contact / Note

1:1
Fully supported

MyProsperity live balance sheets and cashflow reports are generated dynamically from connected accounts and are not stored as exportable records. The most recent snapshot values migrate as custom fields on Contact. The underlying report format cannot be reproduced in Freshsales — advisers use Freshsales custom reports and dashboards to rebuild this view.

Myprosperity

Digital Signature / Annature Record

maps to

Freshsales

Note / Freshsales Files

1:1
Fully supported

MyProsperity's Annature e-signing integration produces signed document records. These are preserved as Freshsales Notes or Files with the signer's contact link. The cryptographic signature metadata is stored as a custom text field. Annature itself is not connected in Freshsales — your team configures a fresh e-signing integration post-migration.

Myprosperity

Lead (from adviser referrals)

maps to

Freshsales

Lead

1:1
Fully supported

Referral leads generated through MyProsperity's lead-generation tools migrate as Freshsales Leads. The lead source field maps to Freshsales Lead Source. Any lead score assigned in MyProsperity migrates to a custom numeric field Lead_Score__c on the Lead object. If the source system records multiple lead statuses, they map to Freshsales Lead Status pick‑list values, ensuring consistent pipeline reporting.

Myprosperity

Deal / Engagement Record

maps to

Freshsales

Opportunity (Deal)

1:1
Fully supported

MyProsperity tracks client engagement events (portal logins, document views, goal completions) but has no deal pipeline. We surface these as a Freshsales Opportunity named after the engagement type with Amount=0 and a custom Stage='Client Engagement'. This lets advisers report on client lifecycle within Freshsales pipelines.

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 logo

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

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • MyProsperity financial data is snapshot-only — live feeds cannot migrate as streams

    MyProsperity's investment feeds (Xplan, Macquarie) pull live portfolio data into the portal dynamically — they are not stored as exportable records. FlitStack migrates the last-synced snapshot values as custom fields on the Contact, but ongoing balance updates stop after cutover. Your team must rebuild the live feed connection in Freshsales via Freshworks integrations, Zapier, or a custom API integration. This is not a data-loss risk — it is a feature gap that must be planned post-migration.

  • Freshsales API rate limits vary by plan and can throttle bulk migration loads

    Freshsales enforces per-plan API rate limits: Growth 1,000 requests/hour, Pro 2,000 requests/hour, Enterprise 5,000 requests/hour. A large MyProsperity account (50,000+ Users with relationships and documents) can exceed these limits during bulk load. FlitStack throttles writes using the account's confirmed plan tier and implements retry-with-backoff on 429 responses. If your account uses the Growth plan and has over 15,000 records, we recommend upgrading to Pro for the migration window or purchasing an API rate-limit add-on from Freshworks before the migration runs.

  • Relationship types require custom field creation before migration maps can validate

    MyProsperity's relationship_type field uses integer codes (0=Owner, 1=Accountant, 2=Lawyer, 3=Wife, 4=Husband, 5=Child) that have no equivalent in Freshsales Contacts. Freshsales does not have a native family-relationship field — FlitStack creates a custom Relationship_Type__c pick-list field and maps each integer code to its label. This field must be created in Freshsales Admin Settings before migration validation runs. We provide a setup checklist that includes this field creation step. The field must be created in Freshsales Admin under Contact fields, with each code mapped to a descriptive label such as Owner, Accountant, Lawyer, or Family.

  • Annature e-signing records carry forward but the integration does not

    MyProsperity's Annature integration produces signed document records with metadata (signer, timestamp, document URL). These records migrate to Freshsales Notes and Files, preserving the document and signer data. However, the Annature connection itself is MyProsperity-specific — Freshsales has no Annature native integration. Your team must configure a separate Annature account and Freshsales integration post-migration if you want new documents to flow automatically. Existing signed records are fully preserved. After the migration, any new e-signed documents should be linked manually or through a rebuilt Annature-to-Freshsales webhook to maintain continuity.

  • Balance sheet and cashflow reports are dynamically generated and not stored as records

    MyProsperity generates live balance sheets, cashflow reports, and tax summaries from connected bank accounts and investment feeds — these are not stored as discrete data records. They cannot be exported as structured data. FlitStack migrates the last-known snapshot values as custom fields on the Contact. The dynamic report format must be rebuilt in Freshsales using Freshsales custom reports, dashboards, and any connected financial data sources your team configures post-migration. To replicate the cashflow view, configure Freshsales custom report tables to pull the migrated snapshot fields and combine them with any new bank feed integrations.

Migration approach

Six steps for a successful Myprosperity to Freshsales data migration

  1. Audit MyProsperity schema and relationship taxonomy

    FlitStack connects via scoped read access to your MyProsperity API and exports all Users, Relationships, Documents, and financial property fields. We audit the relationship_type distribution (how many Owner vs Accountant vs Family records exist), identify records without email addresses, and flag documents over Freshsales' 25MB file-size limit. This audit produces a migration plan that lists every custom field to create in Freshsales before data lands.

  2. Create Freshsales custom fields and the Financial_Asset__c object

    Using the schema audit, FlitStack delivers a step-by-step setup checklist for your Freshsales admin. This includes creating Relationship_Type__c pick-list, Client_Tier__c pick-list, all financial snapshot fields, and the Financial_Asset__c custom object with its Contact__c lookup. We provide field IDs and API names so the migration can reference them during load. This step runs in parallel with your team setting up Freshsales users and assigning licences.

  3. Resolve MyProsperity staff users to Freshsales owners by email

    MyProsperity Practice Portal staff (Adviser, Paraplanner, Admin) are matched to Freshsales Users by email address. For each unmatched staff member, FlitStack generates a warning listing the email address and asks your admin to either invite the user to Freshsales or assign their contacts to a fallback owner before the migration window opens. No Contact migrates without a resolved OwnerId — this prevents orphaned records.

  4. Run sample migration and field-level diff

    A representative slice of 100–300 MyProsperity records — spanning different relationship types, document counts, and financial property values — migrates to Freshsales first. FlitStack generates a field-level diff report comparing source values against the Freshsales loaded values for every mapped field. You review the Relationship_Type__c labels, Financial_Asset__c lookups, and Note attachments before committing the full run. Any mapping errors are corrected in the migration plan before the full dataset loads.

  5. Execute full migration with delta-pickup window

    The full dataset migrates to Freshsales: Users to Contacts/Leads, Relationships to custom fields and Contact Roles, Documents to Notes and Files, and financial properties to Financial_Asset__c records. A delta-pickup window of 24–48 hours captures any MyProsperity records created or modified during the cutover window. FlitStack produces an audit log of every record created, updated, or skipped. One-click rollback reverts the Freshsales environment to its pre-migration state if reconciliation fails.

Platform deep dives

Context on both ends of the pair

Myprosperity logo

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
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 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 Myprosperity and Freshsales.

  • Object compatibility

    B

    2 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

    Myprosperity: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Myprosperity to Freshsales 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 Myprosperity to Freshsales data migrations

Answers to the questions buyers ask most during Myprosperity to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Myprosperity to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most MyProsperity-to-Freshsales migrations complete in 3–7 days for under 25,000 records. Accounts with 25,000–100,000 records or complex financial-property schemas extend to 10–18 days. The longest phase is the Freshsales custom field setup (Financial_Asset__c object, Relationship_Type__c pick-list) and the sample migration diff review. Freshsales API rate limits on Growth plans (1,000 req/hr) also extend load duration — upgrading to Pro before migration significantly reduces clock time.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Myprosperity.
Land in Freshsales, 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