Financial Service Cloud Standard Features vs Managed Package

If you're an existing Financial Services Cloud user, you can continue to use the managed package features. Salesforce hasn’t yet decided about the end of life for the managed package. However, it’s recommended that you evaluate the standard financial account data model and assess the transition path to ensure alignment with the Salesforce standard platform.

If you’re a new Financial Services Cloud user, Salesforce recommends that you use the standard features and minimize the use of managed package features to align with Salesforce strategy about standard platform features. If there are features in the package that you want to use, reach out to your account team.

Here are a few migration guidelines.

Review the new features and consider whether it’s worth switching from the managed package to standard features.

Before you decide to migrate, it’s important to thoroughly understand the similarities and differences between the standard and managed package features that are available in both.

If you decide to migrate from the managed package data model to the standard data model:

• Consider all the dependencies, such as independent software vendors (ISVs) or partner apps on your existing data model.

• Plan any metadata or data migration and thoroughly test them in your sandbox.

Plan your metadata and data migration before you start using the standard Financial Account and its related objects. To understand the object and field mapping between the managed package and standard objects, see API Mapping between the managed package and standard objects.

Thoroughly review the documentation for the standard objects to understand the fields, picklists, and any other details.

Consider the effort and complexity involved in customizing the objects to suit your business needs.

When the Financial Account Management Standard Objects setting is turned on and you have the Financial Services Managed managed package installed, both standard objects and objects from the managed package are visible in your org. It's important to consistently use either the Financial Services Cloud managed package objects or the standard objects, and avoid mixing both when setting up the financial account and its related features.

The Financial Account standard object doesn’t support record types. As an alternative, you can break up your financial account record details with Dynamic Forms. With Dynamic Forms, you can migrate the fields and sections from your page layout to individual components in Lightning App Builder.

Prebuilt field validations aren’t shipped for the Financial Account and related standard objects. For example, the end date must be after the start date. Salesforce recommends you to add the field validations according to your business needs.

For the Financial Account standard object, field encryption is supported only for the Name and Financial Account Number fields.

When installing the CRM Analytics app, manually enable access to all fields. Even after assigning the FSC Analytics Integration permission set to the Analytics Integration User, some fields in standard objects remain restricted due to field-level security.

Starting in Spring ’25, the auto-generated prefix for the financial account party record name is changed from FAR to FAP. To ensure continued functionality and accuracy of the records, review and update any object records, custom queries, Apex class queries, and report filters that currently use the FAR prefix to the new FAP prefix.