Migrate from Myprosperity to HubSpot

Myprosperity contact records map 1:1 to HubSpot contacts. First name, last name, email, phone, address, and job title transfer directly. Financial profile fields (ABN, net worth, investment data) require custom HubSpot contact properties. Primary adviser association becomes a HubSpot contact association.

Myprosperity stores net worth, investment holdings, insurance data, and risk profile as client‑level fields. These map to HubSpot custom contact properties created before migration, using matching data types such as number for net worth, single‑line text for holdings, pick‑list for risk profile, and multi‑line text for insurance details. Field labels and types are agreed upon during planning to ensure a clean import.

Myprosperity Starter and Pro subscription tiers map to HubSpot deals named by client with subscription type and fee amount as deal fields. The subscription tier label becomes a custom deal property. Pro additional client fees are captured as a line-item or custom deal field.

Myprosperity client household or entity records map to HubSpot companies. Company name, ABN/ACN, address, and industry code transfer directly. Because HubSpot lacks an Australian business number field, ABN and ACN are created as single‑line text properties on the Company object. The industry code is mapped to HubSpot’s industry pick‑list, with any unmatched values added as custom options. Custom fields are provisioned before the migration run to avoid import errors.

Myprosperity relationship labels such as Owner, Accountant, and Lawyer map to HubSpot contact‑to‑contact associations. Each association type is stored as a custom property named "relationship_type" on the association, preserving the original role. When a client has multiple advisers, the primary adviser becomes the first association, while others are added as secondary associations. This structure mirrors Myprosperity’s hierarchy and allows filtering contacts by role in HubSpot reports.

Myprosperity document records and Annature e-signature metadata map to HubSpot engagement notes with original timestamps. The e-signature status (signed, pending, expired) is preserved as a note property. Document files are re-uploaded to HubSpot's file storage and linked to the contact record.

Myprosperity connects to XPLAN, Macquarie, and other investment platforms for live data feeds. These references have no HubSpot equivalent. We preserve the feed source and last-sync reference as a custom contact property and create a note documenting the integration — the feed must be reconnected manually post-migration.

Myprosperity Practice Portal staff records (advisers, compliance coordinators, admin staff) map to HubSpot user accounts. Staff role and permission level are preserved as custom user properties. Staff must be provisioned as HubSpot users before migration so their IDs can be matched to owner assignments on migrated contacts and deals.

Myprosperity to‑dos and reminders linked to client records map to HubSpot tasks with the client contact as the parent record. Original due dates, task descriptions, and completion status are preserved, while priority level is recorded as a custom task property. Completed tasks migrate as closed HubSpot tasks, and overdue tasks are flagged with a reminder note. This ensures the task history is visible in the contact’s timeline after migration.

Myprosperity's Xero Practice Manager and XPLAN sync settings are platform‑specific integrations that cannot migrate to HubSpot. FlitStack exports a detailed configuration summary, including connection credentials (where accessible), sync frequency, and mapped entities. Your implementation team can use this summary to rebuild the integrations in HubSpot via the native HubSpot‑Xero connector, XPLAN’s API, or a third‑party middleware such as Zapier or Workato, restoring automated data flow after migration.

Myprosperity Customised Fact Find survey responses map to HubSpot custom contact properties or engagement notes. For structured survey data such as multiple‑choice answers, custom pick‑list properties are created, each labelled with the original question text. Open‑text responses are stored as engagement notes attached to the contact, preserving the full answer and the response timestamp. This approach maintains both the structured data for reporting and the detailed context for future reference.

Myprosperity goal tracking and wealth snapshot reports are generated documents with no HubSpot native equivalent. We preserve the most recent snapshot as a HubSpot file attached to the contact record and surface goal labels as custom deal properties on any linked opportunity or subscription deal.

Annature e-signature integration in Myprosperity tracks document signing status, signer identity, and timestamp. This metadata maps to HubSpot engagement notes with a custom status pick-list (Sent, Viewed, Signed, Expired). The actual e-signature workflow must be rebuilt in HubSpot with DocuSign or HelloSign.

Myprosperity property and car valuations (one-time or monthly) are financial asset data points with no HubSpot equivalent. We preserve the most recent valuation amount and valuation date as custom contact properties, and attach the full valuation history as a note on the contact record.

Myprosperity's digital document signing allocation (1,200–5,000 per tier) is a platform quota, not a CRM data record, so it does not transfer to HubSpot. After migration, document signing usage is governed by your HubSpot subscription limits and any integrated e‑signature tool such as DocuSign or HelloSign, which provide their own quota tracking. FlitStack notes the original allocation for reference during transition, but no quota data is written to HubSpot.