CRM migration

Migrate from Myprosperity to Nutshell

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

Myprosperity logo

Myprosperity

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

12 of 13

objects map 1:1 between Myprosperity and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Myprosperity is a client wealth-management portal built for financial advisers and accountants, tracking client contacts (People), entities (Companies), and the relationships between them (Owner, Accountant, Lawyer, Family). It stores custom properties for financial goals, investment holdings, superannuation, insurance, and documents. Nutshell is a sales CRM using People (contacts), Companies (accounts), Leads, Deals, Tasks, and Activities with an open JSON-RPC API supporting both read and write operations. The migration carries Myprosperity People records as Nutshell People, Myprosperity Companies as Nutshell Companies, and relationship types as custom fields on both objects. Custom financial properties (goals, holdings, policies) migrate to Nutshell custom fields that your team configures post-import. FlitStack sequences the migration so People and Companies load before relationship links resolve, then handles document re-hosting to Nutshell's file storage. Nutshell's rate limits on find operations require batched extraction from Myprosperity's API, and the JSON-RPC write path allows FlitStack to push records directly into Nutshell without CSV intermediaries. Workflows, automations, and document templates in Myprosperity do not migrate — FlitStack exports definitions as rebuild references for your destination-side setup.

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

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Myprosperity objects map to Nutshell

Each row shows how a Myprosperity object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Myprosperity

Person

maps to

Nutshell

People

1:1
Fully supported

Myprosperity Person records map directly to Nutshell People. The primary contact fields (name, email, phone, address) transfer as direct mappings. Nutshell People support custom fields for Myprosperity's relationship_type integer and any client-specific metadata that doesn't map to a native Nutshell field.

Myprosperity

Person (unassigned entity)

maps to

Nutshell

Lead

1:many
Fully supported

Myprosperity Person records that have no linked Entity (orphaned contacts or prospects without an established entity) route to Nutshell Leads. FlitStack flags these during pre-migration validation so your team can review the split before the migration runs.

Myprosperity

Company

maps to

Nutshell

Company

1:1
Fully supported

Myprosperity Company (entity) records map to Nutshell Companies. Entity name, address, and contact details transfer as direct field mappings. Parent-child entity hierarchies in Myprosperity map to Nutshell's Company parent link if the destination has this configured.

Myprosperity

Relationship

maps to

Nutshell

Custom Field + Person-Company Link

1:1
Fully supported

Myprosperity Relationship records encode the relationship type as an integer (0=Owner, 1=Accountant, 2=Lawyer, etc.). Nutshell has no native relationship object. FlitStack writes the relationship type as a custom pick-list field on the linked Person record and maintains a mapping table for post-migration reference. If a Person has multiple relationships to the same Company, FlitStack creates a custom field to capture the full list.

Myprosperity

Task

maps to

Nutshell

Task

1:1
Fully supported

Myprosperity Tasks map to Nutshell Tasks with the same name, due date, status, and assigned owner. Owner assignment resolves via email match against Nutshell users. Open and completed status maps directly; custom task categories from Myprosperity transfer as a custom field on Nutshell Tasks.

Myprosperity

Document

maps to

Nutshell

File (attached to Person or Company)

1:1
Fully supported

Myprosperity documents attached to Person or Company records re-upload to Nutshell Files and attach to the corresponding People or Company record. FlitStack downloads files from Myprosperity and pushes them to Nutshell's file storage, respecting the 25MB per-file limit. Documents without a linked record are attached to the primary contact.

Myprosperity

Financial Goal (custom property)

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Myprosperity custom properties for financial goals, retirement targets, and savings milestones have no native Nutshell equivalent. FlitStack migrates these as custom text or currency fields (Goal_Name__c, Goal_Amount__c) on the Nutshell Person. Your admin creates the custom field definitions in Nutshell before the migration runs.

Myprosperity

Investment Holding (custom property)

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Investment holdings, portfolio values, and asset allocations stored as Myprosperity custom properties migrate to custom fields on Nutshell People. FlitStack creates a structured mapping for multi-field investment data (Asset_Class__c, Current_Value__c, Acquisition_Date__c) to preserve data granularity.

Myprosperity

Superannuation (custom property)

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Superannuation fund details, balance, and contribution history from Myprosperity custom properties migrate as custom fields on Nutshell People (Super_Fund__c, Super_Balance__c, Contribution_Frequency__c). Multi-fund scenarios create multiple custom field entries per Person.

Myprosperity

Insurance Policy (custom property)

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Life insurance, income protection, and health insurance details from Myprosperity migrate as custom fields on Nutshell People. FlitStack maps policy type, provider, sum insured, and premium to separate custom fields for each policy type present in the source data.

Myprosperity

Bank Account (custom property)

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

Bank account details stored in Myprosperity migrate as custom fields on Nutshell People. FlitStack handles account number masking during transfer, preserving the last four digits in Bank_Account_Last4__c while omitting full account numbers from the migration payload.

Myprosperity

System ID

maps to

Nutshell

Source_System_ID__c (custom field)

1:1
Fully supported

Myprosperity's internal record ID is stored as a custom field on each Nutshell record for traceability and delta-run de-duplication. This field is indexed so FlitStack can match records on re-migration without creating duplicates.

Myprosperity

Created Date

maps to

Nutshell

Original_Create_Date__c (custom field)

1:1
Fully supported

Nutshell's CreatedDate is set at migration time and cannot be backdated via the API. FlitStack preserves the original Myprosperity created date as a custom datetime field (Original_Create_Date__c) on each record for reporting continuity and audit purposes.

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

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Relationship model requires post-migration custom field setup

    Myprosperity's Relationship object encodes role types as integers (0=Owner, 1=Accountant, 2=Lawyer, 3=Wife, 4=Husband, 5=Child) linked between Person and Company. Nutshell has no native relationship object — Person-to-Company links are a single lookup field. FlitStack migrates relationship types as a custom pick-list field (Relationship_Type__c) on the Person record and stores a relationship mapping table. For clients with multiple relationship types to the same entity, your Nutshell admin needs to decide whether to stack custom fields, use a text area, or collapse to a primary relationship. We surface the full relationship graph in the pre-migration report so this decision can be made before data lands.

  • Nutshell rate limits on find operations require batched extraction

    Nutshell's API rate limits find requests (findPeople, findCompanies) when non-stub responses are requested. Myprosperity's API extracts all Person and Company records in bulk. FlitStack batches extraction from Myprosperity and writes to Nutshell using individual get/put operations to stay within Nutshell's write limits. The migration plan sequences 500-1000 records per batch with retry logic for 429 responses. Large datasets (50,000+ records) may require extended cutover windows due to rate-limit backoff during the extraction phase.

  • Custom financial properties need Nutshell admin coordination

    Myprosperity's financial data model (goals, investments, superannuation, insurance, bank accounts) stores this data as custom properties per client. Nutshell has no native financial data fields — every financial attribute requires a custom field created in Nutshell before the migration runs. FlitStack generates the custom field specification (name, type, pick-list values if applicable) as part of the migration plan. If your Nutshell account has field limits or your admin hasn't created the custom fields before migration day, those properties land in a staging table for post-migration bulk update.

  • Document re-hosting required for file attachments

    Myprosperity documents attached to Person or Company records are stored in Myprosperity's file storage. Nutshell attaches files directly to People or Company records with a 25MB per-file limit. FlitStack downloads each document from Myprosperity and re-uploads to Nutshell, attaching to the corresponding record. Documents exceeding 25MB are flagged in the pre-migration report and require either compression or splitting before migration. Documents without a linked record are attached to the primary contact person for that client.

  • Workflows and automations do not transfer

    Myprosperity's workflow automations (document request sequences, task triggers, reminder rules) and any custom automation logic do not have a native equivalent in Nutshell. FlitStack exports your Myprosperity workflow definitions as a structured rebuild reference (JSON/YAML) that your Nutshell admin can use to reconstruct automation rules in Nutshell's sales automation builder. The rebuild reference is delivered alongside the migration data and does not add to migration time — it's generated during the pre-migration audit phase.

Migration approach

Six steps for a successful Myprosperity to Nutshell data migration

  1. Audit Myprosperity data model and relationship graph

    FlitStack connects to Myprosperity's API and exports a full data inventory: all Person records, Company records, Relationship links, Tasks, Documents, and custom properties. We build a relationship graph showing each Person's linked Companies and relationship type integers. The audit report identifies orphaned records (Person with no Company link), entities with multiple linked Persons, and custom properties that need Nutshell custom fields. This report drives the custom field specification your admin creates before migration day.

  2. Create Nutshell custom fields and coordinate admin setup

    Based on the audit, FlitStack generates a custom field specification for your Nutshell admin: field names, types (text, currency, pick-list, date), and pick-list values for relationship types and entity types. Your admin creates these fields on the People and Company objects before the migration window. FlitStack validates the field configuration against the specification before writing any data.

  3. Migrate Companies before People, then resolve relationship links

    FlitStack sequences the migration so Companies load first so Account IDs are available when People records write. Each Person record is linked to its primary Company via the Nutshell Company field. Relationship type integers are written to the Relationship_Type__c custom field at this stage. For Persons with multiple Company links, FlitStack stores the additional links in a relationship mapping table for post-migration review and manual linking in Nutshell if needed.

  4. Run sample migration with field-level diff

    A representative sample (100-500 records spanning Persons, Companies, Tasks, and records with custom financial properties) migrates first. FlitStack generates a field-level diff report comparing source values against destination field values, flagging any mapping discrepancies before the full run. You review the diff, confirm relationship type mapping and custom field populations, and approve the full migration.

  5. Full migration with delta-pickup and file re-hosting

    The full migration pushes all Person, Company, Task, and Relationship records to Nutshell via the JSON-RPC API. Documents are downloaded from Myprosperity and re-uploaded to Nutshell Files, attached to the corresponding People or Company record. A 24-48 hour delta-pickup window captures any records modified in Myprosperity during cutover. FlitStack generates an audit log of every record written, and one-click rollback reverts the Nutshell account to its pre-migration state if reconciliation fails.

  6. Deliver relationship mapping table and workflow rebuild reference

    After migration completes, FlitStack delivers a relationship mapping table (CSV) showing each Myprosperity Person ID, their linked Companies, and the relationship type integer for manual review. The workflow rebuild reference documents every Myprosperity automation in a format your Nutshell admin can use to reconstruct rules in Nutshell's sales automation builder. FlitStack support is available for 30 days post-migration for field corrections and re-migration of any incorrectly mapped records.

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

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

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

  • 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 Nutshell 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 Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Myprosperity-to-Nutshell migrations complete in 48–72 hours for datasets under 10,000 Person and Company records. The pre-migration audit and custom field coordination typically takes 3–5 business days before migration day. Large datasets with dense relationship graphs (50,000+ records or entities with multiple linked Persons) extend to 5–10 days, primarily due to Nutshell's rate limits on find operations requiring batched extraction and the relationship resolution step. Custom field creation by your Nutshell admin is the most common scheduling dependency.

Adjacent paths

Related migrations to explore

Ready when you are

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