CRM migration
Field-level mapping, validation, and rollback between Myprosperity and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Myprosperity
Source
Freshsales
Destination
Compatibility
11 of 12
objects map 1:1 between Myprosperity and Freshsales.
Complexity
BStandard
Timeline
3–7 days
Overview
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.
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.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Freshsales
Contact
1:1MyProsperity 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
Freshsales
Lead
1:manyMyProsperity 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
Freshsales
Contact Role / Custom Pick-list Field
1:1MyProsperity 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
Freshsales
Note / Freshsales Files
1:1MyProsperity 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)
Freshsales
Custom Object: Financial_Asset__c
1:1MyProsperity 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
Freshsales
Freshsales User
1:1MyProsperity 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
Freshsales
Custom Field on Contact / Account
1:1MyProsperity 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
Freshsales
Custom Field on Contact
1:1MyProsperity 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
Freshsales
Custom Field on Contact / Note
1:1MyProsperity 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
Freshsales
Note / Freshsales Files
1:1MyProsperity'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)
Freshsales
Lead
1:1Referral 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
Freshsales
Opportunity (Deal)
1:1MyProsperity 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.
| Myprosperity | Freshsales | Compatibility | |
|---|---|---|---|
| User | Contact1:1 | Fully supported | |
| User | Lead1:many | Fully supported | |
| Relationship | Contact Role / Custom Pick-list Field1:1 | Fully supported | |
| Document | Note / Freshsales Files1:1 | Fully supported | |
| Financial Property (asset, valuation) | Custom Object: Financial_Asset__c1:1 | Fully supported | |
| Practice Portal Staff User | Freshsales User1:1 | Fully supported | |
| Investment Feed | Custom Field on Contact / Account1:1 | Fully supported | |
| Client Subscription Tier | Custom Field on Contact1:1 | Fully supported | |
| Balance Sheet / Cashflow Report | Custom Field on Contact / Note1:1 | Fully supported | |
| Digital Signature / Annature Record | Note / Freshsales Files1:1 | Fully supported | |
| Lead (from adviser referrals) | Lead1:1 | Fully supported | |
| Deal / Engagement Record | Opportunity (Deal)1: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.
Myprosperity gotchas
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
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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
Myprosperity
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Myprosperity and Freshsales.
Object compatibility
2 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
Myprosperity: Not publicly documented.
Data volume sensitivity
Myprosperity 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 Myprosperity to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Myprosperity to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Myprosperity
Other ways to arrive at Freshsales
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.