Financial Service Cloud Standard Features vs Managed Package

Guidelines for Existing and New Financial Services Cloud Users

If you’re an existing Financial Services Cloud (FSC) user, you can continue to use the managed package features.
Salesforce hasn’t yet announced an end-of-life date for the managed package.

However, it’s recommended that you evaluate the standard financial account data model and assess a possible transition path to ensure alignment with Salesforce’s long-term standard platform strategy.

If you’re a new Financial Services Cloud user, Salesforce recommends using the standard features and minimizing the use of managed package components.
If there are certain managed package features you want to use, reach out to your Salesforce account team.

Migration Guidelines

Before deciding to migrate, thoroughly understand the similarities and differences between the standard and managed package features.
Below are some key steps and recommendations for planning a smooth transition.

1. Evaluate the New Features

Review the new standard platform features and determine whether the benefits justify switching from the managed package to the standard model.

2. Assess Dependencies

If your org relies on ISVs or partner applications, evaluate their dependencies on your current data model.
Changing your model may impact integrations or app functionality.

3. Plan Metadata and Data Migration

Plan both metadata and data migration carefully, and test everything thoroughly in your sandbox before moving to production.
To understand object and field mappings between managed package and standard objects, refer to the API Mapping documentation provided by Salesforce.

4. Review Standard Object Documentation

Study the standard object documentation to understand fields, picklists, and relationships.
Consider the effort and customization complexity required to match your business processes.

5. Avoid Mixing Object Models

When the Financial Account Management Standard Objects setting is turned on and you have the FSC managed package installed, both object sets become visible.
It’s crucial to choose one approach — either managed package or standard objects — and avoid mixing both in your implementation.

6. Record Types and Dynamic Forms

The Financial Account standard object doesn’t support record types.
As an alternative, use Dynamic Forms to organize fields and sections directly in the Lightning App Builder for greater flexibility.

7. Field Validations

Prebuilt field validations aren’t included for Financial Account and related standard objects (for example, ensuring the End Date is after the Start Date).
Add your own validation rules to enforce data integrity according to business requirements.

8. Field Encryption Support

For the Financial Account standard object, field encryption is supported only for the following fields:

• Name

• Financial Account Number

9. CRM Analytics Integration

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

10. Prefix Change (Spring ’25 Update)

Starting with Spring ’25, the auto-generated prefix for the Financial Account Party record name changes from FAR to FAP.
To ensure continued functionality:

• • Review and update all object records,

  • Adjust any custom queries, Apex code, and report filters
    that currently use the FAR prefix to the new FAP prefix.