Why do advisory firms switch CRMs?
Most wealth management firms we hear from are doing one of three things: consolidating after an acquisition, moving off an advisor-specific CRM onto Salesforce or HubSpot so the whole firm works in one system, or leaving a product whose ownership and roadmap have changed.
The category has changed hands a lot. Redtail is owned by Orion. Salentica now sits under SS&C Black Diamond. Junxure was renamed AdvisorEngine CRM in 2022. Each change prompts firms to ask whether to stay or move.
FlitStack AI handles the move: data out of the old CRM with its history, into Salesforce or HubSpot, with the new system set up around it.
What makes a wealth management migration different?
Three things, compared with a typical sales CRM:
- Households. Clients are grouped into households with roles (primary, spouse, dependant, trustee). A contact-and-company CRM has no native household, so the model has to be designed, not copied.
- Long relationships. Advisors keep notes and activities for decades. Losing original dates breaks review history and makes the CRM hard to defend in an audit.
- Systems around the CRM. Custodial feeds, portfolio management and financial planning tools connect to the CRM. Their links need a plan before cutover.
What does each source give you?
| Source | How data comes out | What to plan for |
|---|---|---|
| Redtail CRM | A full database backup on admin request (zip, MySQL format), plus bulk contact exports to spreadsheet | Email archives are a separate support request; a database backup needs mapping, not just a CSV upload |
| Salentica Elements | Runs on Salesforce, so data is in Salesforce objects | Moving to Salesforce can mean re-modelling inside the same platform family |
| Salentica Engage, Tamarac | Built on Microsoft Dynamics 365 | Data comes out through Dynamics; see our Dynamics 365 to Salesforce and Dynamics 365 to HubSpot pages |
| AdvisorEngine CRM (Junxure) | Export path confirmed during scoping | Custom fields from years of use |
| Wealthbox | Export path confirmed during scoping | Often a small-firm CRM moving up to Salesforce |
These sources aren’t on FlitStack AI’s standard connector list. We scope each one on the call and confirm whether we connect through the underlying platform or work from the export.
Some destination vendors also offer migration help. Wealthbox, for example, says it performs data migrations into Wealthbox from other CRMs. If Wealthbox is your destination, ask them first.
Salesforce or HubSpot?
| Salesforce (Agentforce Financial Services) | HubSpot | |
|---|---|---|
| Household view | Built for it: Salesforce describes a single household view that combines CRM and financial system data | Households modelled as companies or a custom object |
| Integrations | Custodial and wealthtech integrations are a stated focus | Marketing, email and client service in one system |
| Admin effort | Needs an admin or partner | Easier for a small operations team to run |
For the Salesforce route, see Salesforce implementation. For HubSpot, see HubSpot implementation.
How does FlitStack AI run the migration?
- Scoping call. Source, destination, record counts, household model and integrations. You get a written quote within one business day.
- Audit and design. We profile the source data and agree the household model, field mapping and value maps.
- Sample migration. A set of real households moves first, and advisors check them in the new CRM.
- Full run and cutover. The production migration, then a delta sync for anything changed during the project.
- Validation and support. A field-level validation report, one-click rollback if the run fails validation, and 14 days of direct support from a migration engineer.
Process setup (pipelines for new clients, workflows for reviews and onboarding, permissions by team) can be part of the same project.
What should you prepare for the scoping call?
- Record counts by object: households, contacts, notes, activities and documents.
- The systems around the CRM that send or receive data, and who owns each one.
- Retention rules for what must stay in the old system or an archive.
- A target date for cutover, so the delta sync can be planned around it.
Where does FlitStack AI fit?
If you’re moving an advisory firm’s CRM and want households, notes and history intact, with a validation report before you switch, book a scoping call. Use the CRM migration checklist to prepare.

