Key Takeaways
- A typical Junxure to Salesforce Financial Services Cloud migration takes 6 to 9 months end-to-end for a 30–150 advisor wealth-management firm.
The most expensive mistake is migrating Junxure first and your portfolio system second — a parallel migration uses one cut-over weekend, one training cycle, one integration build.
- Household modelling decisions made before configuration begins save four to eight weeks of late-stage rework.
- Junxure activity history is mostly noise — migrating open tasks plus the last 24 months covers 95%+ of advisor lookups.
- The post-go-live support curve is the single best adoption-health signal — healthy migrations stabilise at 4–8 hours/month of support by month three.
Why Wealth Firms Are Re-Evaluating Junxure in 2026
Junxure has been a steady fixture in wealth-management practices for more than two decades. Generations of advisors have built their books around it. But for a growing number of firms, “still works” is no longer compelling enough. The roadmap has slowed under successive ownership changes. Advisors are juggling more systems than ever — Orion, Black Diamond, eMoney, Schwab, Fidelity, DocuSign, Microsoft 365, and asking the legacy CRM to be the unifying surface is a stretch it was never designed for.
Compliance demands keep rising. Younger advisors expect the kind of unified, mobile, AIassisted workflow they get in every other part of their lives. And agentic AI has shifted from “interesting tech” to a meaningful operating-cost lever.
The destination most of these firms are choosing is Salesforce Financial Services Cloud (FSC) — increasingly with Agentforce layered on top. Navirum has been delivering these migrations to wealth advisors for over seven years and was recognized as a Salesforce Ridge Partner in February 2026. Across our migration portfolio, the projects that succeed look notably different from the ones that struggle — and the differences are rarely in the headline architecture. They’re in the operational decisions that generic migration guides skip over.
Here are five lessons that have made the biggest difference in the field.
Lesson 1 — The Parallel Migration Pattern: Move Junxure and Your Portfolio System Together
Most Junxure firms run a portfolio management system alongside it: usually Orion or Black Diamond, sometimes Tamarac or Addepar. The natural-feeling plan is to migrate the CRM first, get stable, and tackle the portfolio integration as a Phase 2. In practice, that sequence is more expensive, more disruptive, and produces a worse result. Each phase needs its own cut-over weekend, its own training cycle, and its own change-management push with advisors. And the FSC architecture you build in Phase 1 will need to be re-engineered in Phase 2 once portfolio data arrives — because the household, account, and g
The Parallel Migration Pattern brings both systems into FSC together, using a scheduled, queueable integration architecture so the portfolio system pushes balances and positions onto the right Household automatically from day one. Advisors land in a system that is already complete: the household record shows the relationships and the money, in the same view, on go-live morning. One cut-over, one training cycle, one moment of advisor change.
Across our wealth-management migrations, parallel migration has consistently delivered faster time-to-value and better adoption than sequenced migration. If your portfolio integration cannot be ready in the same window, treat that as a project sequencing problem worth solving — not a reason to settle for a sequenced migration.
Lesson 2 — The Household Model Workshop: Decide Before You Configure
FSC’s Household object is one of the most powerful things about the platform — and one of the most opinionated. It can elegantly model multi-generational families, business entities, trusts, joint accounts, and the relationships between them. But the model is a structural decision, and getting it wrong is the single most common cause of late-stage rebuilds we see.
Junxure tends to encourage firms to evolve their household conventions implicitly over time. By migration time, two advisors in the same firm often have meaningfully different mental models of what counts as a household and how to handle entities like grantor trusts, family LLCs, retirement plans for closely-held businesses, or split-engagement couples.
The Household Model Workshop is a structured pre-build session with your advisors, operations team, and compliance lead. Document the decisions explicitly:
- How are multi-generational households represented?
- How do business entities relate to individual owners?
- How are trust structures (revocable, irrevocable, grantor, family) modelled?
- How do joint accounts roll up to household-level reporting?
- How are household membership changes (births, marriages, deaths, divorces) handled?
Get sign-off in writing before any FSC configuration begins. Across our migration portfolio, this single workshop typically saves four to eight weeks of late-stage rework. The cost of running it is one afternoon. The cost of skipping it is a rebuild.
Lesson 3 — The Linked Document Strategy: Don’t Rebuild Your DMS
Junxure firms typically arrive with decades of household documents — financial plans, tax returns, beneficiary forms, scanned meeting notes, custodian statements — sitting on a P Drive, a SharePoint site, or a document management system like NetDocuments or Laserfiche. The conventional advice is to migrate all of it into Salesforce Files as part of the project.
For most wealth firms, this is months of low-value work. The volume is enormous, the documents are heterogeneous, and the metadata to associate each one with the right Household is rarely clean. Across our wealth-management migrations, we routinely see firms underestimate this part of the project by an order of magnitude — and the work consumes time that should have gone into adoption and integration.
The Linked Document Strategy keeps your existing document repository where it is and links it at the Household level using a Salesforce Hyperlink Formula field. Any user clickingthe household record opens the right folder in one click. Advisors get the unified surface they wanted; the firm avoids a multi-month document migration; and you can layer in a proper DMS integration (NetDocuments, SharePoint, Box, OneDrive) in a later phase if you decide it adds value. This is the kind of pragmatic decision that does not appear in vendor decks but materially changes project economics.
Lesson 4 — The 24-Month Activity Filter Rule: Junxure History Is Mostly Noise
Junxure firms often arrive with tens of thousands of historical tasks and activities accumulated over fifteen or twenty years. The instinct is to bring it all across “for completeness.” Don’t.
Across our wealth-management migration audits, the proportion of those records that any advisor will ever open again post-migration is in the low single digits. Bringing them across pollutes FSC, slows reports and dashboards, complicates Agentforce later (agents that scan activity histories produce more confident nonsense the noisier the history is), and forces every user into a system that feels heavier than it should.
The 24-Month Activity Filter Rule: migrate all open tasks, plus the last 24 months of completed activity, and archive the rest. Make it a written rule before the migration starts, sign it off with operations and compliance, and document the archive location for the rare audit query. Most firms find the 24-month window covers more than 95% of the lookups they actually need, and the platform people spend their day on is dramatically faster and cleaner.
The same principle applies to inactive contacts, dormant households, and unused custom fields. Migration is a one-time opportunity to leave the ballast behind.
Lesson 5 — The 12–20 Hour Adoption Curve: Use the Support-Hours Pattern as a Health Check
The most reliable signal we know for whether a migration has actually landed is not advisor sentiment, training-completion rates, or system usage logs. It’s the support-hours curve.
Across Navirum Orbit Managed Services engagements, a healthy Junxure-to-FSC migration consumes:
- Months 1–2: 12 to 20 hours per month of post-go-live support (refining workflows, adding fields, training new joiners, tuning automations, fixing the inevitable small things that only emerge once people are using the system in anger).
- Month 3 and beyond: 4 to 8 hours per month, sustained as the new baseline for ongoing optimisation.
This is The 12–20 Hour Adoption Curve. If your support consumption is materially higher than that at month three, or if it is flat rather than falling, something has not landed. Usually one of two things: data quality work was not deep enough (so users are repeatedly hitting the same friction), or adoption is patchy (so a small group of power users is masking a larger group of advisors who quietly went back to spreadsheets and email).
Treat this curve as a project metric. Bridge the first ninety days with a managed-services partner so the curve has somewhere to live, then reassess. If you are not seeing the falling pattern by month three, run a structured adoption review — do not assume it will fix itself.
When to Add Agentforce: Migration First, Integration Second, Agents Third Junxure firms looking at FSC are increasingly asking the same follow-up question: when do we add Agentforce? The answer that holds up across our engagements is third. Migration first, integration second, agents third. Agents on top of clean data, integrated systems, and consistent workflows are remarkable. Agents on top of legacy data, half-finished integrations, and inconsistent processes produce confident nonsense. The order of operations matters more than the timeline. Once a firm is settled on FSC with a clean household model, integrated portfolio data, a working document linkage strategy, and a stable adoption curve, layering Agentforce becomes an additive project.
The agents wealth firms typically deploy first are:
Long-tail care agents — handle birthdays, seasonal touches, renewal nudges, and follow-up cycles that historically slipped between the cracks.
Client onboarding and KYC agents — collect, validate, and structure new-client information; flag exceptions; reduce a multi-day workflow to hours.
Meeting prep and advisor research agents — assemble a unified household briefing (positions, plan progress, last activity, life events, action items) before every client meeting.
Compliance and beneficiary review agents — proactively scan for review-due triggers, generate tasks, and document the audit trail.
Junxure vs Salesforce FSC vs FSC + Agentforce: Capability Comparison
| Capability | Junxure | Salesforce FSC | FSC + Agnetforce |
| Household & relationship modelling | Limited (contact + custom workarounds) | Native, multi generational, entity aware | + AI-assisted relationship suggestions |
| Portfolio data integration (Orion, Black Diamond) | One-off, manual reconciliation | Bidirectional via scheduled queueable APIs | + Real-time agent driven insights |
| Document management | Local P Drive / SharePoint dependency | Native Salesforce Files + DMS integrations | + Automated document classification |
| Compliance + audit trail | Manual workflows | Built-in with custom Flows | + Automated review agents |
| Advisor experience | Contact + activity log paradigm | Unified household command centre | + Conversational AI assistant |
| Vendor roadmap | Slowed under successive ownership | Continuous quarterly Salesforce releases | + Agentforce roadmap (rapid) |
| AI / Agentic capabilities | None native | Einstein, native AI features | Full Agentic AI platform |
| Mobile experience | Limited | Full Lightning mobile experience | + Mobile AI assistants |
| Workflow automation | Limited | Salesforce Flow + automation | + Agent orchestrated workflows |
| TCO trajectory | Stable but ceiling bound | Higher initial, scalable | Highest initial, lowest TCO at scale |
Frequently Asked Questions
How long does a Junxure to Salesforce FSC migration take?
A typical Junxure to Salesforce Financial Services Cloud migration takes 6 to 9 months end-to-end for a 30–150 advisor wealth-management firm. Foundation and data work runs 8–12 weeks; integration and configuration runs 8–14 weeks; cut-over, training, and adoption runs 4–8 weeks.
Can Junxure data be exported to Salesforce?
Yes. Junxure data — contacts, households, activities, custom fields, and notes — can be exported and imported into Salesforce Financial Services Cloud. The work is in mapping, cleansing, and household reconstruction rather than the export itself. Plan a structured data assessment phase before configuration begins.
Should I migrate all my Junxure activity history to Salesforce?
No. Across our migration audits, only a low-single-digit percentage of historical activity records are ever opened again post-migration. Apply the 24-Month Activity Filter Rule: migrate all open tasks plus the last 24 months of completed activity, and archive the rest. This covers 95%+ of advisor lookups and keeps FSC fast and clean.
How much does a Junxure to Salesforce FSC migration cost?
Costs vary by firm size, integration complexity, and data quality. Most wealth-management firms allocate 5–10% of their overall Salesforce project budget to migration and data readiness specifically. Talk to a partner like Navirum for a fixed-fee scope.
Should Junxure and my portfolio management system (Orion or Black Diamond)
migrate together?
Yes. The Parallel Migration Pattern is consistently faster and cheaper than a sequenced approach. Migrating Junxure and your portfolio system into Salesforce FSC at the same time uses one cut-over weekend, one training cycle, and one integration build — and avoids re-engineering the household model in a Phase 2.
Do I need to migrate documents from my P Drive or SharePoint into Salesforce Files?
Usually not. The Linked Document Strategy keeps your existing document repository where it is and uses a Salesforce Hyperlink Formula field on the Household record to open the relevant folder in one click. This avoids months of low-value document-migration work and lets you layer in a proper DMS integration later if needed.
When should I add Agentforce after migrating from Junxure?
After migration and integration are stable. The sequence is: migration first, integration second, agents third. Agents perform brilliantly on top of clean data and well-integrated systems. They produce confident nonsense on top of dirty data. Most firms add Agentforce in the second or third quarter post-go-live.
What is the typical adoption curve after a Junxure to FSC go-live?
The 12–20 Hour Adoption Curve: 12 to 20 hours per month of support consumption in the first 60 to 90 days, falling to 4 to 8 hours per month by month three. If you are not seeing this falling pattern by month three, run a structured adoption review — usually data quality or adoption gaps are the cause.
Why are wealth firms migrating away from Junxure in 2026?
Four pressures usually appear together: an uncertain Junxure roadmap under successive ownership, a hard integration ceiling (modern wealth practices touch ten or more systems), an advisor experience gap (younger advisors expect Salesforce-class interfaces), and the AI moment (Agentforce is meaningfully faster on FSC than on legacy CRMs).
Does Salesforce Financial Services Cloud replace the need for a separate portfolio management system?
No. FSC is a CRM and advisor-experience platform. Portfolio management systems like Orion, Black Diamond, Tamarac, and Addepar continue to handle portfolio accounting, performance reporting, and rebalancing. The win is integrating them with FSC so advisors get a unified surface — not replacing them.
Glossary
- Junxure — Customer relationship management software historically popular with U.S. wealth-management advisors. Currently owned by AdvisorEngine.
- Salesforce Financial Services Cloud (FSC) — Salesforce’s industry-specific platform for wealth management, banking, and insurance, with native household, financial account, goal, and asset/liability objects.
- Agentforce — Salesforce’s enterprise AI agent platform, designed to deploy specialised AI agents on top of Salesforce data including FSC.
- Household modelling — The structural representation of multi-person, multigenerational, multi-entity client relationships within a CRM.
- Hyperlink Formula field — A Salesforce field type that creates a clickable link from a record to an external URL or local resource path.
- Queueable integration — A Salesforce architecture pattern using scheduled, queue-based processing for high-volume bidirectional data sync. –
- Orbit Managed Services — Navirum’s predictable, retainer-based post-go-live support offering for Salesforce wealth-management implementations.
About the author
Rory Galvin is the founder and CEO of Navirum, a boutique Salesforce, Agentforce, and AI consultancy focused exclusively on wealth management and financial services. Navirum is a Salesforce Ridge Partner and has delivered Financial Services Cloud migrations and Agentforce implementations to wealth advisors across North America for over seven years. Connect with Rory on LinkedIn or read more at navirum.com/blog.
Related reading
- The Complete Guide to Redtail Migration: Integrating Agentforce with Salesforce Financial Services Cloud
- 5 conseils pour la mise en œuvre de Salesforce Financial Services Cloud
- Powerful Tips for Salesforce CRM to Financial Services Cloud Migration
- 5 Powerful Reasons Why RIAs Choose Salesforce Financial Services Cloud
