Adoption path for existing managed package customers
Key Takeaway
Existing managed package customers can keep using package features. Salesforce recommends that they evaluate the standard financial account data model and assess a transition path, but moving is a decision, not a requirement.
Many existing Agentforce Financial Services customers built their orgs on the managed package, which ships its own objects, fields, and components. Many of the same capabilities, such as financial accounts and groups and households, now also exist as standard platform features that need no package. The adoption path is how an existing package customer decides whether to move to those standard features, and how to plan the move safely. The path matters because a move touches existing customizations and any apps that depend on the current data model.
What Salesforce recommends
If you're an existing managed package customer...
You can keep using managed package features. Salesforce hasn't decided on an end of life for the package. Salesforce recommends that you evaluate the standard financial account data model and assess a transition path, so your org stays aligned with the standard platform.
If you're a new customer...
Salesforce recommends that you use standard features and keep managed package use to a minimum. If you want a feature that exists only in the managed package, reach out to your account team.
For an existing customer, moving is a decision, not a requirement. Start by reviewing the new standard features and deciding whether switching is worth it. Salesforce doesn't recommend uninstalling the managed package, including for customers who decide to migrate to the standard data model.