Migrate from Myprosperity to Zoho CRM

MyProsperity person records (first_name, last_name, email, phone, address) map directly to Zoho Contact fields. The Contact becomes the primary record for each client in Zoho CRM. If the person has no associated company in MyProsperity, they land in Zoho as a standalone Contact without an AccountId.

MyProsperity relationship field values (0=Owner, 1=Accountant, 2=Lawyer, 3=Wife, 4=Husband, 5=Child) are translated into Zoho Contact Role pick-list values (Decision Maker, Financial Adviser, Legal Adviser, Family Member, etc.). Each MyProsperity person-to-primary-client relationship generates a Zoho Account Contact Relation with the appropriate role.

MyProsperity adviser records are matched to Zoho CRM Users by email address. Each adviser record in MyProsperity becomes a User record in Zoho so that record ownership and assignment rules work correctly. Unmatched adviser emails are flagged for manual User creation before migration.

MyProsperity stores financial goal data (property valuations, savings targets, retirement goals) as structured properties per person. These map to custom fields on the Zoho Contact record (Goal_Type__c, Goal_Amount__c, Goal_Deadline__c) or a dedicated Goals custom module linked by a lookup to Contact.

MyProsperity documents (wealth reports, cashflow snapshots, tax documents) are re-uploaded as Zoho Attachments on the relevant Contact or Account record. Each attachment preserves its original filename and upload timestamp. Zoho's 25MB per-file limit applies — large PDFs are flagged for splitting.

MyProsperity may hold company associations for business clients. These map to Zoho Accounts using the company name as Account Name. Website, industry, and employee count fields map where present. Parent-child company hierarchies in MyProsperity map to Account.Parent_Account lookup in Zoho.

MyProsperity subscription tier (Starter, Pro) and client subscription count are stored as custom fields on the Contact record (MyProsperity_Subscription_Tier__c, Client_Subscription_Count__c). This preserves billing history context in Zoho for finance and client success teams. These custom fields enable finance teams to track subscription history, run revenue‑based reports, and segment clients by tier, while client‑success managers can quickly view the original MyProsperity plan when reviewing accounts.

MyProsperity to-do reminders (document requests, e-signature follow-ups) map to Zoho Tasks. Original due dates and assigned users are preserved. Recurring reminders map as a single Task with the original recurrence pattern noted in the description field. Each task inherits the original priority level and status, and the related Contact or Account lookup is set so the task appears in the client’s activity timeline. Overdue items retain their original due date.

MyProsperity calendar events map to Zoho Events with start time, end time, and venue preserved. Events linked to a Contact or Account in MyProsperity retain that association via the WhatId field in Zoho. Invitees are not migrated — Zoho Events invitee management is destination-side.

MyProsperity live financial data feeds (bank balances, investment portfolios, property valuations) have no native Zoho CRM equivalent. FlitStack preserves the most recent snapshot as a formatted Note attachment or a custom module record. Financial feed automation must be rebuilt using Zoho Finance integrations post-migration.

MyProsperity's custom-branded portal and mobile app configuration is platform-specific and does not carry over. Zoho offers Canvas for UI customization and Zoho Mobile — branding must be rebuilt from scratch as part of Zoho setup. Administrators should define brand colours, upload logos, configure custom domains in Zoho Canvas, and set up Zoho Mobile profiles for iOS and Android. Client communication will guide users to the new interface.

MyProsperity workflow rules (document reminders, goal progress alerts, balance notifications) are not migratable. FlitStack exports the rule definitions as a reference document. Rebuild using Zoho Blueprint (Professional+) or Workflow Rules and Deluge scripts post-migration. The exported reference lists each rule’s trigger, condition set, and actions, enabling Zoho admins to recreate equivalent Blueprint processes or Deluge scripts. Post‑migration testing should validate that newly created automations fire correctly under the same scenarios.