The hard part of this move is not the export. It is the difference in how the two systems think. AdvisorEngine CRM works in contact records; Wealthbox works in contact records. Get that mapping wrong and every report built on it afterwards is wrong too. This page covers the field map, what does not survive, what it costs, and the reconciliation step that decides whether anyone trusts Wealthbox in month two.
The two systems, side by side
| AdvisorEngine CRM | Wealthbox | |
|---|---|---|
| Primary record | Contact | Contact |
| Grouping | Household and relationship links | Household, as a first-class record |
| Activity history | Actions, notes and a deep workflow engine | Notes, tasks, events and email history on the contact |
| Documents | Attached to the contact record | Files on the contact or household |
| Getting data out | CSV export per module, or a vendor-assisted extract. | CSV export, a documented API, and a migration team that maps the source for you. |
| Who administers it | Ops staff, with vendor support for workflow changes. | None. An operations associate can run it. |
| Pricing | Custom quoted. | $35 to $65 per user per month billed annually, or $59 to $99 monthly. |
What breaks
- Grouping changes: Household and relationship links becomes Household, as a first-class record. Somebody has to define what a group means in the target before load.
- Activity history moves with partial fidelity. AdvisorEngine CRM stores it as actions, notes and a deep workflow engine; Wealthbox expects notes, tasks, events and email history on the contact.
- Automations, reports, dashboards and permissions never transfer. Budget them as build work.
- Every connected system has to be repointed and retested: the DMS, billing, e-signature and the shared inbox.
Known hazards on each side
Leaving AdvisorEngine CRM:
- The workflow engine is the reason firms stayed, and it is the part that does not migrate.
- Long-tenured orgs carry a decade of custom fields and inconsistent picklists.
- Desktop-era Junxure history may need a vendor extract rather than a self-service export.
Arriving in Wealthbox:
- Wealthbox documents that recurring-task future occurrences cannot be imported from Redtail.
- Contact Type absorbs the source system's status field, and Deceased or Inactive values also flip the Wealthbox Status field.
- Servicing and Writing Advisor fields are mapped to Assigned To or a custom contact role, which is a decision someone has to make.
The field map
| Concept | In AdvisorEngine CRM | In Wealthbox | What to watch |
|---|---|---|---|
| Primary record | Contact | Contact | Same shape. Mostly a mechanical load. |
| Grouping | Household and relationship links | Household, as a first-class record | The target groups records differently, so grouping is created rather than copied. |
| Activity history | Actions, notes and a deep workflow engine | Notes, tasks, events and email history on the contact | Expect partial fidelity. Types, timestamps and authorship survive; structure often does not. |
| Documents | Attached to the contact record | Files on the contact or household | Usually a separate extract and load from the record data. |
| Owner and assignment | Assigned user or advisor fields | Assigned user or team fields | Map departed staff explicitly. Records assigned to nobody disappear from every view. |
| Custom fields | Firm-specific fields added over time | Created to match, or consciously dropped | The audit here is the work. Undocumented fields that reports depend on are the usual surprise. |
Cost and timeline
| Phase | Typical range |
|---|---|
| Data audit and cleanup | $3,000 to $25,000 |
| Migration execution | $5,000 to $50,000 |
| Target configuration | Two to six weeks |
| Ongoing administration | Absorbed by existing operations staff |
The five phases
- Audit AdvisorEngine CRM. Count records per object, find duplicates and orphans, and decide what does not come with you. Get that decision signed off before mapping.
- Map against real records. Use the table above as the starting point, then walk fifty live records field by field.
- Dry run into a Wealthbox sandbox. Load the full set, not a sample. Sample loads hide the failures that only appear at volume.
- Cut over on a quiet window. Freeze writes in AdvisorEngine CRM, load, repoint every integration, unfreeze. Keep AdvisorEngine CRM read-only for at least a quarter.
- Reconcile. Compare Wealthbox to AdvisorEngine CRM record by record and field by field, and produce a variance report.
The full version of this plan, with the failure evidence behind it, is in the CRM migration playbook.
The compliance clause
The Advisers Act books-and-records rule (17 CFR 275.204-2) survives the migration. A household that lands without its history is a records gap, not a cosmetic issue. Keep the field map, the variance report and the mapping sign-offs with the records, because the decisions you made in phase two are part of the record too.
Where Caddi fits
Caddi does the mechanical half and then keeps doing it. Show it the task once and it reads AdvisorEngine CRM, applies your field map, loads Wealthbox, and then compares both sides record by record and hands back a variance report you can act on. Because it runs over APIs across your stack, the same agent covers the parts a migration tool ignores: documents filed to the right contact with the right metadata, and the post-cutover hygiene that otherwise becomes someone's Monday.
Caddi automation for these systems: AdvisorEngine CRM and Wealthbox.
Related migrations
- Redtail CRM to Wealthbox
- Salesforce Financial Services Cloud to Wealthbox
- Salesforce to Wealthbox
- Wealthbox to Redtail CRM
- Wealthbox to Salesforce
- Wealthbox to Salesforce Financial Services Cloud
Migration without the manual pass
Move and reconcile AdvisorEngine CRM into Wealthbox
Caddi reads AdvisorEngine CRM, applies your field map, loads Wealthbox, then compares both sides record by record and reports the variances.
Frequently asked questions
How do you migrate from AdvisorEngine CRM to Wealthbox?
Audit the AdvisorEngine CRM data first, then map fields against fifty real records rather than against the schema, dry run the full set into a Wealthbox sandbox, cut over on a quiet window with writes frozen, and reconcile record by record afterwards. CSV export per module, or a vendor-assisted extract. Wealthbox then needs the records loaded in dependency order, with documents as a separate pass.
What does not transfer from AdvisorEngine CRM to Wealthbox?
Grouping changes: Household and relationship links becomes Household, as a first-class record. Somebody has to define what a group means in the target before load. Activity history moves with partial fidelity. AdvisorEngine CRM stores it as actions, notes and a deep workflow engine; Wealthbox expects notes, tasks, events and email history on the contact. Automations, reports, dashboards and permissions never transfer. Budget them as build work.
How long does a AdvisorEngine CRM to Wealthbox migration take?
Six to twelve weeks is realistic for a clean mid-size move, and three to six months where Wealthbox is being implemented at the same time. Firms with years of history in AdvisorEngine CRM should budget several weeks of cleanup before any data moves.
Who administers Wealthbox afterwards?
None. An operations associate can run it. That is one of the reasons this move is lighter than a platform migration.
What are the compliance implications for advisory firms?
The Advisers Act books-and-records rule (17 CFR 275.204-2) survives the migration. A gap in client history is a finding, so keep the field map, the variance report and the sign-offs where an examiner can find them.