TL;DR / Key Takeaways
- What is it? A comprehensive guide to understanding the differences between Salesforce FSC Core and the FSC Managed Package, and how to plan your migration
- Key Benefit: FSC Core unlocks Agentforce AI agents, modern data architecture, improved performance, and all future Salesforce financial services innovation — the managed package will not receive these capabilities
- Best For: RIAs, wealth management firms, banks, insurance companies, and any financial services organization currently on the FSC managed package evaluating a transition to FSC Core
- Cost/Investment: Migration typically requires 6-16 weeks and $40,000-$150,000+ depending on customization complexity, integrations, and data volume
- Bottom Line: Salesforce hasn't announced an end-of-life date for the managed package, but all future innovation — including Agentforce, Compliance Navigator, and advanced AI — is exclusive to FSC Core. The question isn't whether to migrate, but when.
If your financial services firm runs Salesforce Financial Services Cloud, you're facing one of the most consequential technology decisions of 2026: stay on the FSC managed package or migrate to FSC Core.
Salesforce launched FSC in 2016 as a managed package — a pre-built set of objects, fields, and code installed as an add-on to the core Salesforce platform. It gave financial services firms an industry-specific data model for client management, householding, and financial account tracking without building everything from scratch.
Starting in 2019, Salesforce began rebuilding FSC natively on the core platform. That effort has accelerated dramatically, and the message from Salesforce is now unmistakable: FSC Core is the future. The managed package is not being abandoned — but it is being left behind by innovation.
Here's what that means in practical terms:
| Capability | FSC Managed Package | FSC Core |
|---|---|---|
| Agentforce AI agents | ❌ Not available | ✅ Pre-built agents for meeting prep, follow-up |
| Compliance Navigator | ❌ Not available | ✅ Real-time compliance monitoring (roadmap) |
| Flexible Hierarchy Management | ❌ Not available | ✅ Multi-entity visualization (Spring '26) |
| Financial Account Balance History | ❌ Single overwritable balance | ✅ Full balance history records |
| Multi-owner Financial Accounts | ❌ Primary/Joint Owner lookups | ✅ Junction object for unlimited owners |
| Modern Household Model | ❌ Account record types | ✅ Party Relationship Groups |
| Summary & Record Rollups | ❌ Rollup by Lookup Rules | ✅ Configurable native rollups |
| Data Cloud Integration | Limited | ✅ Full native integration |
| Future Salesforce Releases | Minimal updates | ✅ All new features and innovation |
If you're evaluating Agentforce, Data Cloud, or any advanced Salesforce capability for financial services — you need FSC Core. There is no alternative path.
The shift from managed package to FSC Core isn't just a version upgrade — it's a fundamental change in how your financial services data is modeled and managed. Understanding these differences is essential for planning your migration.
Managed Package: Ownership is driven by two lookup fields — Primary Owner and Joint Owner. This is simple but limiting. A financial account can only have two owners, and one must be designated as primary.
FSC Core: Ownership uses a junction object called Financial Account Party. This creates a many-to-many relationship between Accounts (clients) and Financial Accounts, allowing: - Unlimited owners per financial account - Flexible role definitions (primary, joint, beneficiary, trustee, custodian) - No requirement to designate a single primary owner
Why this matters: In wealth management, ownership structures are rarely as simple as one or two people. Trusts, partnerships, corporate accounts, and multi-generational family structures require flexibility that the managed package can't provide.
Managed Package: A single balance field on the Financial Account object. When a balance is updated (manually or via integration), the previous balance is overwritten. No history.
FSC Core: Balances are stored as records in a Financial Account Balance child object. Each update creates a new record, maintaining a complete history of account balances over time.
Why this matters: Balance history is essential for performance reporting, trend analysis, and compliance documentation. It also eliminates the Apex trigger performance issues that plague managed package environments during nightly custodial data loads.
Managed Package: Households are modeled using Account record types — a Business Account record type represents the household, with individual Contact records associated to it.
FSC Core: Households use a two-object model: 1. Business Account — functions like any standard Salesforce account 2. Party Relationship Group — defines the Business Account as a Household and stores household-specific information
Party Relationship Groups support: - Multiple relationship types within a household - Cross-household relationships - Group-level rollups and analytics - A setup wizard for creating new households
Why this matters: The Party Relationship Group model is more flexible and extensible than the record type approach. It supports complex family structures, multi-generational households, and entity relationships that are common in wealth management and private banking.
Managed Package: Uses a Relationship Map component that visualizes connections between accounts and contacts.
FSC Core: Replaces the Relationship Map with the Actionable Relationship Center (ARC) — a more powerful visualization tool that allows users to: - View hierarchical and lateral relationships - Take actions directly from the relationship map (create tasks, send emails, update records) - Configure relationship types and display rules - Model complex multi-entity structures
Managed Package: Uses Rollup by Lookup Rules with Apex triggers. This approach has known performance limitations, especially during high-volume data loads from custodial integrations. Nightly batch updates can cause trigger conflicts and processing delays.
FSC Core: Uses configurable Record Rollups and Summary Rollups built natively into the platform: - Record Rollups aggregate related records (e.g., all cases for household members) without Apex triggers - Summary Rollups aggregate financial account balances using the Financial Account Summary object - No Apex trigger dependencies means better performance during data loads - Real-time rollup options available
Why this matters: If your firm has ever experienced slow nightly data loads, trigger conflicts, or stale rollup data, FSC Core's native rollup architecture directly addresses these pain points.
Migrating from the FSC managed package to FSC Core is a significant but manageable project. The key is thorough planning, methodical execution, and testing at every stage.
Before touching any configuration, document your current environment:
Data Model Inventory: - Which managed package objects are you using? (Financial Account, Financial Account Role, etc.) - What custom fields have you added to managed package objects? - Are you using custom objects for financial services data? - How are households currently structured?
Integration Map: - Which custodial feeds update financial accounts? (Schwab, Fidelity, Pershing, etc.) - What third-party AppExchange packages depend on managed package objects? - How do portfolio management integrations (Orion, Black Diamond) interact with your data model? - Are financial planning tools (MoneyGuidePro, eMoney) integrated?
Customization Audit: - Custom Apex triggers on managed package objects - Workflow rules and Process Builder flows that reference managed package fields - Reports and dashboards built on managed package data - Lightning pages and components that use managed package components
ISV Dependency Check: This is critical. Some third-party AppExchange packages may depend on managed package objects. Verify with each vendor whether they support FSC Core's standard objects. If they don't yet, you may need to plan your migration timeline around their roadmap.
Map your current configuration to the FSC Core equivalent:
| Managed Package Element | FSC Core Equivalent |
|---|---|
| Financial Account (managed package) | Financial Account (standard object) |
| Primary Owner / Joint Owner lookups | Financial Account Party junction object |
| Balance field on Financial Account | Financial Account Balance child records |
| Account record type: Household | Business Account + Party Relationship Group |
| Rollup by Lookup Rules | Record Rollups + Summary Rollups |
| Relationship Map | Actionable Relationship Center (ARC) |
| Custom fields on managed package objects | Recreate on standard objects |
| Record types on managed package objects | Recreate on standard objects |
Salesforce provides detailed field mapping documentation: - Financial Account metadata mapping - Groups and Households mapping
Important: FSC Core can coexist with the managed package. You don't have to rip out the managed package before building FSC Core objects. This allows for a phased migration.
Configuration steps: 1. Enable Financial Account Management Standard Objects in Setup 2. Recreate custom fields on standard objects (map from managed package equivalents) 3. Configure Financial Account Party relationships for multi-owner modeling 4. Set up Party Relationship Groups for household management 5. Configure Record Rollups and Summary Rollups to replace Rollup by Lookup Rules 6. Set up the Actionable Relationship Center to replace the Relationship Map 7. Recreate Lightning pages using standard object components 8. Update automations (Flows, triggers, Process Builder) to reference standard objects 9. Rebuild reports and dashboards on standard objects
Data migration is typically the most complex phase:
Pro tip: Run the migration in a sandbox first. Validate record counts, field mapping accuracy, and relationship integrity before touching production. We typically run 2-3 migration cycles in sandbox before the final production migration.
This is where ISV dependencies become critical:
Risk: You migrate to FSC Core, and a critical AppExchange package breaks because it depends on managed package objects. Solution: Inventory every third-party package. Contact each vendor. Get written confirmation of FSC Core support before migrating.
Risk: You have dozens (or hundreds) of custom fields on managed package objects that need to be recreated. Solution: Generate a complete field inventory early. Map every field, including field type, picklist values, validation rules, and dependencies.
Risk: During a phased migration, some data lives in managed package objects and some in standard objects, creating inconsistencies and reporting gaps. Solution: Define clear boundaries. Migrate by entity type (all financial accounts at once, all households at once) rather than incrementally.
Risk: Leadership dashboards and compliance reports break because they reference managed package objects. Solution: Inventory all reports and dashboards early. Rebuild them on standard objects in the sandbox and validate before go-live.
Risk: After migration, rollup data is stale or incorrect because the new rollup engine hasn't processed historical data. Solution: Plan for a full rollup recalculation after data migration. Budget time for the processing to complete.
This is the question every financial services firm on the managed package is asking. Here's our framework:
Our general recommendation: If you're not migrating now, you should be planning for it. Every month you wait is a month of innovation you're not accessing.
Here's something many firms don't realize: you don't have to uninstall the managed package to start using FSC Core features. Both can coexist in the same org.
This means you can: 1. Enable FSC Core standard objects 2. Begin configuring new features (ARC, Party Relationship Groups, Financial Account Balance) 3. Run new records through FSC Core while legacy records remain on managed package objects 4. Migrate data gradually (though we recommend entity-by-entity migration for consistency)
This coexistence approach reduces risk and allows for a phased transition. However, avoid running parallel systems indefinitely — the goal should be full migration within a defined timeline.
Salesforce has not announced an end-of-life date for the managed package. However, all new features, AI capabilities (Agentforce), and innovation are being built exclusively for FSC Core. The managed package will continue to receive maintenance updates but no significant new functionality.
No. The pre-built Agentforce agents for wealth management require FSC Core standard objects. If you want to deploy Agentforce AI capabilities, you must migrate to FSC Core.
Depending on complexity: 6-16 weeks from planning through go-live. Simpler environments with fewer customizations and integrations can complete in 6-8 weeks. Complex environments with extensive custom code, multiple ISV dependencies, and large data volumes may require 12-16 weeks.
Implementation costs typically range from $40,000 to $150,000+ depending on the scope of customization, number of integrations, data migration complexity, and testing requirements. There are no additional Salesforce licensing costs — FSC Core is included in the FSC license.
Potentially, if they reference managed package-specific objects or fields. This is why the ISV dependency check and integration update phases are critical. With proper planning, integration disruption can be minimized to the cutover window.
We strongly recommend it — especially for firms with complex environments. FSC Core migration touches your data model, integrations, automations, reports, and user experience. A partner with financial services expertise and FSC Core migration experience can identify risks early, avoid common pitfalls, and ensure your compliance requirements are maintained throughout the transition.
At Vantage Point, we've been implementing Salesforce Financial Services Cloud since its inception — across both the managed package and FSC Core. Our senior, US-based consultants understand the technical nuances, integration challenges, and compliance requirements that make financial services migrations unique.
Whether you're ready to migrate now or want to build a timeline for the next 6-12 months, we'll help you plan a path that minimizes risk and positions your firm for every capability Salesforce is building for financial services.
Contact us today to start your FSC Core migration assessment.
Vantage Point is a leading Salesforce and HubSpot consultancy specializing in regulated industries. With 150+ clients, 400+ engagements, a 4.71/5.0 average client rating, and an employee-owned team of senior consultants, we deliver compliance-first CRM implementations for financial services, insurance, healthcare, and beyond.