Migrate from Myprosperity to Twenty CRM

MyProsperity clients map directly to Twenty People records. The client name splits into firstName and lastName on import. Email, phone, and job title transfer as standard fields. The MyProsperity client ID is stored as a custom Source_System_ID__c field for traceability and delta-run de-duplication.

MyProsperity Company records map 1:1 to Twenty Company objects. Company name, domain/website, industry, employee count, and address fields transfer as standard Company fields. Parent-child company hierarchies in MyProsperity map to Twenty's parentCompanyId relation. Circular parent references are detected and flagged before migration to prevent import errors. If a parent company does not exist in the target dataset, the child company is imported without a parent link for manual resolution.

MyProsperity relationship types (Owner=0, Accountant=1, Lawyer=2, Wife=3, Husband=4, Child=5) are typed links between clients and companies. We map these to Twenty's generic relation system with a custom RelationType__c field holding the MyProsperity integer value and label. This preserves the relationship semantics without losing context.

MyProsperity documents attached to clients and companies migrate as Twenty Notes with the file reference stored in the Note body or as an external URL link. If the document lives in MyProsperity's storage, we flag it as a manual re-upload item in the migration plan. Original upload dates and author references are preserved as custom datetime and user fields.

MyProsperity tasks and reminders map to Twenty Tasks with standard fields: title, due date, assignee, and completion status. The original task description transfers to the Task body. Completed-at timestamps map to completedAt where available. Recurring task patterns in MyProsperity are flagged as custom notes since Twenty's native recurrence model differs; your team recreates recurring schedules in Twenty's task builder post-migration.

MyProsperity Starter vs Pro client subscription tier is a billing flag with no direct Twenty equivalent. We migrate this as a custom select field (Client_Tier__c) on People with values Starter and Pro. The tier determines which advisory features were available in MyProsperity and provides context for continuity in Twenty.

MyProsperity investment feeds from XPLAN, Macquarie, and other integrations provide portfolio and balance data on Company records. These custom financial metrics map to custom Number fields on the Twenty Company object. We create fields named by their source (e.g., XPLAN_Balance__c, Macquarie_Portfolio__c) so advisory teams can rebuild dashboards in Twenty.

Any extended client properties stored in MyProsperity beyond standard contact fields migrate as custom fields on the Twenty People object. Field type is determined by the source data type (text, number, date, select). We audit MyProsperity's property schema before migration to capture everything.

MyProsperity Practice Portal staff licenses represent internal team members who access the platform. These map to Twenty WorkspaceMembers. Email and name transfer directly; role-based access in MyProsperity maps to Twenty's permission groups (Admin, Editor, Viewer). Inactive staff accounts in MyProsperity migrate as inactive WorkspaceMembers in Twenty unless your team specifies otherwise. Staff license counts in MyProsperity do not affect the migration cost but determine how many WorkspaceMember seats you need in Twenty.

MyProsperity's activity timeline (client interactions, meeting logs, communication history) has no precise equivalent in Twenty's native model. We migrate key activity summaries as Notes attached to the People record with a custom Activity_Type__c label. Full chronological activity feeds require a custom timeline implementation in Twenty.

MyProsperity's Annature e-signing integration for document signatures has no direct equivalent in Twenty. Completed signatures in MyProsperity are preserved as Notes with signing metadata including signer name, timestamp, and document status. Future signature workflows must be rebuilt using Twenty's webhook system combined with an external e-signing tool such as DocuSign, HelloSign, or Adobe Sign. We provide a webhook configuration guide during migration to help your team set up the new signing pipeline.