Short answer
Moving from the Financial Services Cloud managed package to FSC on core means migrating data and configuration from the packaged FinServ__ objects to Salesforce's standard FSC objects built into the platform. It unlocks new FSC and Agentforce features, which Salesforce now delivers on the standard data model.
Why firms make this move
Financial Services Cloud originally shipped as a managed package with namespaced objects and fields. Salesforce has since rebuilt FSC on standard objects in the core platform, and new capabilities are delivered there. Orgs on the package can keep running, but they miss out on new features over time.
The migration touches every customization that references package objects: fields, automation, reports, integrations and code.
What moves
- Financial accounts, roles and holdings
- Households, relationships and relationship groups
- Goals, life events and referrals
- Automation, reports and dashboards rebuilt against standard objects
- Integrations pointed at the new objects and fields
How the data maps
| From | To |
|---|---|
| FinServ__FinancialAccount__c | Financial Account (standard) |
| FinServ__FinancialAccountRole__c | Financial Account Party / roles |
| Package automation | Flows on standard objects |
| Package reports | Rebuilt reports and dashboards |
What to watch out for
- Hidden dependencies in Apex, flows and integrations
- Reports and dashboards that silently break
- Roll-up and AUM logic that must be revalidated
- Testing effort across every team that uses FSC
How Vantage Point runs the migration
- Dependency inventory across metadata, code and integrations
- Target design on standard objects
- Data mapping and migration scripts
- Rebuild automation, reports and integrations
- Full-sandbox test loads and regression testing
- User acceptance testing
- Cutover and hypercare
Typical timeline
Typically 8 to 16 weeks, depending on customization depth.
Frequently asked questions
Do we have to move off the managed package?
Not immediately, but new FSC and Agentforce features are being delivered on the core data model, so staying on the package means falling behind over time.
Can the migration happen in our existing org?
Yes. It is usually done in place, with careful sandbox testing before switching users over.