Migrate from Myprosperity to Salesforce Sales Cloud

MyProsperity User records map 1:1 to Salesforce Contacts. The primary user (relationship_type 0=Owner) and any household members (relationship_type 3–5) each become individual Contact records linked to a common Account representing the household or individual client. The Account Contact Relationship object captures each person’s role, and non-primary relationships (Accountant, Lawyer) are also stored as separate Contacts on the same Account.

MyProsperity encodes relationships as integers (0=Owner, 1=Accountant, 2=Lawyer, 3=Wife, 4=Husband, 5=Child). Salesforce lacks a built-in relationship-type field, so we define a custom pick-list (Agent_Relationship_Type__c) on Contact, populate it with the matching labels, and map each integer code during the transform step. Your admin then adds the field to the appropriate Contact page layouts and sharing rules.

MyProsperity links users to external financial accounts (XPLAN, Macquarie, and other feeds). These references migrate as custom text fields on the Account record — one field for the external account identifier and one for the feed provider name. Holdings data requires a separate custom object or related list design.

Multiple MyProsperity users sharing a household (e.g., Owner + spouse + child) map to one Salesforce Account representing the family unit, with each user as a Contact on that Account. The Account Contact Relationship object captures the relationship between each person and the household Account.

MyProsperity documents attach to user records. Small documents (<25MB) re-upload to Salesforce Files and link to the corresponding Contact or Account record. Documents exceeding Salesforce's 25MB file limit or with inaccessible download URLs are preserved as Salesforce Notes with the original portal URL stored in a custom field for re-linkage.

MyProsperity tasks (document requests, reminders, to-dos) map to Salesforce Task records with the same subject, status, due date, and original created timestamp. The MyProsperity 'send reminder' flag migrates as a custom checkbox field (Reminder_Flag__c) since Salesforce Task has its own native reminder mechanism.

MyProsperity notes attached to user records migrate as Salesforce Notes linked to the corresponding Contact. Rich-text formatting in MyProsperity notes is preserved as HTML in the Salesforce Note Body field. If MyProsperity stores notes in a separate object, we map them to Salesforce Notes with the parent record ID linking back to the Contact.

MyProsperity's internal user identifier is stored on the Salesforce Contact as a custom text field named Source_System_ID__c. This field enables delta‑run de‑duplication, audit traceability, and cross‑referencing between Salesforce records and the MyProsperity portal after go‑live. It also supports incremental data loads by allowing the extraction job to skip records already present with matching identifiers.

Salesforce sets the system‑generated CreatedDate at the moment of migration, so original MyProsperity create and update timestamps are preserved as custom datetime fields (Original_Create_Date__c and Original_Last_Modified__c) on the Contact. These fields let reports and dashboards display the true client engagement timeline, support data‑quality validation, and enable filters that reference the source system’s history.

Australian financial services firms must retain consent records for SMS and email marketing under ASIC and AFS licence rules. MyProsperity consent flags migrate as custom checkbox fields (SMS_Consent__c, Email_Consent__c) on Contact, preserving the raw on/off state. Your compliance team should audit these values post‑migration, consider adding consent‑date, consent‑channel, and consent‑source fields, and ensure the records satisfy current opt‑in requirements before any marketing communications are sent from Salesforce.

MyProsperity practice portal staff accounts (admins, paraplanners) who do not correspond to client contacts map to Salesforce Users. Owner resolution in Salesforce Opportunities uses email matching — if a MyProsperity staff user email matches a Salesforce User, their MyProsperity tasks assign to that Salesforce User; otherwise tasks are flagged for manual owner assignment.