CRM migration
Field-level mapping, validation, and rollback between Myprosperity and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Myprosperity
Source
Nutshell
Destination
Compatibility
12 of 13
objects map 1:1 between Myprosperity and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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
Nutshell
People
1:1Myprosperity 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)
Nutshell
Lead
1:manyMyprosperity 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
Nutshell
Company
1:1Myprosperity 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
Nutshell
Custom Field + Person-Company Link
1:1Myprosperity 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
Nutshell
Task
1:1Myprosperity 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
Nutshell
File (attached to Person or Company)
1:1Myprosperity 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)
Nutshell
Custom Field on Person
1:1Myprosperity 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)
Nutshell
Custom Field on Person
1:1Investment 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)
Nutshell
Custom Field on Person
1:1Superannuation 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)
Nutshell
Custom Field on Person
1:1Life 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)
Nutshell
Custom Field on Person
1:1Bank 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
Nutshell
Source_System_ID__c (custom field)
1:1Myprosperity'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
Nutshell
Original_Create_Date__c (custom field)
1:1Nutshell'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.
| Myprosperity | Nutshell | Compatibility | |
|---|---|---|---|
| Person | People1:1 | Fully supported | |
| Person (unassigned entity) | Lead1:many | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Relationship | Custom Field + Person-Company Link1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Document | File (attached to Person or Company)1:1 | Fully supported | |
| Financial Goal (custom property) | Custom Field on Person1:1 | Fully supported | |
| Investment Holding (custom property) | Custom Field on Person1:1 | Fully supported | |
| Superannuation (custom property) | Custom Field on Person1:1 | Fully supported | |
| Insurance Policy (custom property) | Custom Field on Person1:1 | Fully supported | |
| Bank Account (custom property) | Custom Field on Person1:1 | Fully supported | |
| System ID | Source_System_ID__c (custom field)1:1 | Fully supported | |
| Created Date | Original_Create_Date__c (custom field)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
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Myprosperity
Source
Strengths
Weaknesses
Nutshell
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 Nutshell.
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 Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Myprosperity to Nutshell 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 Nutshell
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.