Salesforce for Wealth Management Firms: Financial Services Cloud Setup Guide

A wealth advisor may work with 1 person, a married couple, a family trust, and several investment accounts linked to different custodians. A conventional contact record rarely explains those relationships well enough. The firm also needs to know who can view each account, which balances are current, and where meeting notes should be retained.

Salesforce Financial Services Cloud setup begins with those decisions. A dashboard can show client relationships, financial accounts, and upcoming reviews, but the information is useful only when the records beneath it are accurate. Firms that configure pages before settling their data model often have to rebuild permissions and integrations later.

This guide covers Salesforce for wealth management firms using the current financial services platform. It explains the setup sequence for a US advisory business, including existing managed-package environments, the newer standard objects, client households, custodian feeds, and regulated records.

TL;DR

Salesforce Financial Services Cloud setup should begin with licensing and the data model, followed by Person Accounts, household relationships, financial account ownership, and custodian integration. Salesforce now calls the product Agentforce Financial Services, although Financial Services Cloud remains common in its documentation. New implementations generally use standard platform features, while older managed-package organizations need a migration plan before switching object models. Build the Wealth Management Console after the records and access rules work. Test household totals against custody data and verify that advisors cannot open another team’s restricted information. SEC and FINRA duties require separate compliance review. Software configuration alone doesn’t establish regulatory compliance.

What Financial Services Cloud Does for Wealth Management

Salesforce extends ordinary CRM records with financial relationships and advisor workflows. The platform can link an individual client to a household, show relevant financial accounts, record goals, and assign follow-up work. It can also surface information provided by a custodian or another financial application. That makes it useful for relationship management, but it doesn’t automatically replace portfolio accounting, trading, or the firm’s approved financial planning software.

Salesforce’s product terminology changed during 2026. Its current product overview calls Financial Services Cloud Agentforce Financial Services and notes that the former name still appears in applications and help pages. Both terms may appear in licenses, existing configurations, and project discussions. An implementation team should use exact product names when checking entitlements.

For Salesforce for wealth management firms, the immediate goal is to show an advisor the correct client context. A meeting page might contain family relationships, upcoming tasks, and current account information. Client profile information has a different owner from transaction or market data.

A Financial Services Cloud implementation also needs a clear boundary between relationship management and regulated advice. Recording a retirement target in CRM doesn’t prove that a planning calculation was performed. An integration can display account values while leaving trade execution and regulatory books in their approved systems. Decide which processes belong in Salesforce before building them. A firm may have a clean-looking client page while holding duplicate client identities or incorrect account links.

Check Licenses, Users, and Setup Prerequisites

For Salesforce Financial Services Cloud setup, start with the work each person will perform. Advisors may edit client profiles and review household relationships. Client service associates may create tasks and update authorized contact information. Compliance staff may need supervisory access without permission to alter financial account balances. System integration users should receive only the API access their connection requires. These distinctions affect both licensing and permissions.

For current public rates, Salesforce’s sales edition pricing lists Financial Services Cloud Sales Core at $325, Sales Advanced at $500, and Sales Max at $700 per user per month, billed annually, on its US page. They are reference prices, not implementation fees or a promise that every feature is included. The purchased SKU and contract control the firm’s actual entitlements.

These figures are arithmetic examples at public rates. They exclude tax, discounts, setup services, external data products, and additional licenses. The Max price is also a current published offering, but its extra capabilities shouldn’t be assumed necessary for an ordinary advisor rollout. Review required AI and Data 360 features separately before approving them.

Ask whether Person Accounts are enabled and whether the organization already uses the financial services managed package. List the user roles, available test environments, identity provider, and systems that hold the source data.

The project should identify a data owner from advisory operations and an information security reviewer before configuration begins. Without them, the Salesforce administrator can build technically valid objects that represent the wrong relationships.

Choose the Standard or Managed-Package Data Model

This Salesforce Financial Services Cloud setup decision affects nearly every later step. Salesforce delivers most current Financial Services Cloud functions on the core platform without requiring the historic managed package. Existing firms may still use package objects, custom fields, automation, or outside applications built against that older model.

These choices are covered in Salesforce’s implementation considerations, which describe differences between standard and managed-package features and advise reviewing partner dependencies before changing architecture. Salesforce also cautions against uninstalling the managed package as a shortcut. An established firm should plan metadata and data migration in a sandbox before considering a change.

Why Financial Account Ownership Looks Different

In the managed-package approach, ownership can be stored through primary and joint-owner fields on a financial account. In the standard model, Financial Account Party represents the link between an account and a person or organization, with a role such as owner or trustee. Standard balance information may be stored in Financial Account Balance records rather than a single value field on the account.

That distinction matters for joint investment accounts. A married couple may share an account, while a trust has a trustee and beneficiaries with different legal relationships. The firm needs accurate roles without creating a duplicate investment account for every associated person. Salesforce household management cannot repair financial ownership that was mapped incorrectly at import.

For a new Salesforce Financial Services Cloud setup, document object names and API mappings before connecting any data feed. Confirm that the chosen apps use the same model. Turning on standard objects in an org with the old package can make both sets visible; mixing them casually creates confusing reports and relationships.

A Financial Services Cloud implementation can stay on a supported package structure where a dependency requires it.

Create Individual Client Profiles and Person Accounts

Salesforce Financial Services Cloud setup needs one reliable client identity across the firm’s CRM records. An individual may have a personal relationship with an advisor and also act as trustee or business owner. Use a consistent client identifier rather than relying on name matching.

Salesforce explains in its person modeling guide that Person Accounts are the usual model for new financial services implementations. They combine account and contact information in an individual client experience. Salesforce supports the older individual model for firms already using it, so an established org shouldn’t switch without reviewing the migration impact.

Fields to Settle Before Loading Data

Define the client’s full name and preferred contact method, then review what personal information is genuinely needed in CRM. Establish a stable external identifier for matching with approved source systems. Identify relationship owner, servicing team, client status, and relevant consent preferences. Sensitive identifiers require special handling; avoid collecting full tax identifiers in a custom field simply because the field can be created.

Salesforce for wealth management firms should also distinguish prospects from clients under an active advisory relationship. A prospect may have a sales opportunity but no financial account data. The page layout should reflect what the staff member needs to do without exposing unrelated information.

Test conversions and merges on sample records before a large import. Duplicate Person Accounts can cause repeated review tasks, inaccurate household membership, and conflicting advisor ownership. If an outside planning tool uses a different person identifier, document the matching process and the system responsible for correcting mismatches.

The system is easier to maintain when users know which source supplied a client value and who may update it.

Build Households and Map Related People

Salesforce Financial Services Cloud setup uses households to represent shared client relationships. A family may have 2 spouses, children, a trust, and an outside attorney. Some participants belong to the household, while others have a professional role without being part of the family.

The intended structure appears in Salesforce’s household setup example, which walks through a Party Relationship Group, its members, and related businesses. It also shows how an Actionable Relationship Center graph can display the connections.

Household Membership Is Different From Account Access

Salesforce household management requires rules for primary members, household groups, and business relationships. Membership doesn’t itself establish legal ownership of a financial account. A child listed in a household may have no rights to see a parent’s brokerage statement. A trustee may be linked to a trust account but have no permission to review a beneficiary’s unrelated personal account.

Build representative records for a married couple with a joint account, a separate retirement account, and a family trust. Check how each relationship appears to advisors. Then test whether the system counts the joint account only once in a household total, using approved rollup behavior and properly mapped ownership.

Another Salesforce household management requirement appears when clients move households after marriage, divorce, or a change in service relationship. Define who may edit membership and whether prior relationships must be retained for audit or business reference. Avoid silently transferring access when a household record changes.

For Salesforce for wealth management firms, relationship mapping should cover attorneys and other professionals only where the firm has a lawful, current business reason to record them. Store the role, link, and review date. A financial advisor can then understand why the person appears without assuming that every connected party is authorized to receive client information.

Configure Financial Accounts, Balances, and Holdings

Salesforce Financial Services Cloud setup requires accurate financial account links to both the individual client and any authorized household view. Wealth firms may track brokerage accounts, retirement accounts, trusts, and selected bank relationships. Start by identifying the source system, the unique external account ID, and the account type. The record shouldn’t be considered ready until its owners and roles have been checked.

The object model is explained in Salesforce’s standard account guidance, which identifies Financial Account, Financial Account Party, Financial Account Balance, and related standard objects. It recommends planning metadata and data migration when moving away from the managed-package model. These structures allow a firm to represent ownership roles and balance dates more explicitly than a single client-linked amount.

A financial account balance needs a valuation or balance-as-of date. Some data is fit for relationship context but not for financial reporting. Decide which values advisors can rely on for meetings and which must be checked in the custody system.

Salesforce household management also needs rules for account aggregation. Joint accounts can appear under multiple individual profiles, creating a double-count risk if a summary simply adds every related record. The solution must use the firm’s approved household ownership and rollup design. Test joint ownership and beneficiary-only relationships separately.

A mortgage related to several household members shouldn’t produce an inflated debt total. Reconcile source amounts and calculated summaries before enabling a headline household net worth field. Such a summary must have a known calculation method and coverage boundary.

Connect Custodians and Financial Planning Systems

A wealth management CRM integration must answer a precise question: what information moves, from which system, and how often? Custodians usually remain the authoritative source for holdings and account activity, while a portfolio system may calculate performance. Salesforce can organize that information with client relationships and advisor work, but the integration needs controlled identifiers and refresh behavior.

For qualifying Agentic Advisor configurations, Salesforce documents a BridgeFT connector that connects approved custodial data sources. It involves connector setup, advisor identifiers, Data 360, and scheduled synchronization. That example doesn’t mean every firm or custodian receives a built-in connection at no extra cost. Licensing, available data, and configuration must be verified against the intended product.

Design the Feed Before Building the Screen

For each source, record the custodian ID, account number or token, account owner, balance types, holding identifiers, transaction dates, and refresh time. Avoid creating a new Salesforce account whenever a feed uses a slightly different client spelling. Match through governed identifiers, and maintain an exception queue when a match isn’t certain.

A wealth management CRM integration also needs a policy for stale or failed feeds. Show the last successful update when that information matters to the advisor. If a balance fails to arrive, don’t replace it silently with zero. Separate missing information from a confirmed account value of zero.

Consider a fictional firm whose custodian sends daily balances while its planning software receives quarterly assumption updates. Make each source clear on the client page and decide where the advisor should verify the final number before discussing a recommendation.

For every wealth management CRM integration, approve data sharing before deployment. Use a dedicated integration identity with the required object permissions and secure credential handling. Each wealth management CRM integration should also log rejected records and support retry without duplicate financial accounts. Inspect the data provider’s service terms and any required customer consent before moving records.

Set Up Advisor Goals, Onboarding, and Meeting Workflows

Salesforce Financial Services Cloud setup should begin advisor workflows with a small number of repeatable client tasks. Annual reviews, new-client intake, and follow-up after a planning meeting are useful examples. Don’t copy every step from a paper checklist into a CRM field if it would make an ordinary meeting harder to record.

Financial Goals and Financial Plans support goal-oriented records. Salesforce’s goal setup guidance describes permission assignments and OmniStudio components for viewing and editing those records. A firm can track goals such as retirement or education funding, but the projection methodology must come from an approved planning process. A stored progress value isn’t the same as independent investment advice.

Use Action Plans for Repeatable Follow-Ups

Salesforce for wealth management firms can use Action Plans to create assigned tasks from templates. For a client onboarding process, the template might create a client service review task after an advisor confirms the engagement. Salesforce’s Action Plans setup covers permissions, templates, and record-page components. The firm must still define the required approvals and ownership.

Financial Services Cloud implementation teams should test whether template dates account for business calendars and whether unresolved tasks remain visible after the assigned advisor changes. A template is a starting structure; it doesn’t independently verify that a legal document or identity check was completed.

Keep Meeting Notes Controlled

Interaction Summaries can connect notes and next steps to an interaction. Salesforce’s meeting summary guidance describes fields for confidentiality, meeting purpose, and related records. Build a policy for which notes belong in the CRM and which must be stored in an approved records system. A client service associate may need to see an assigned action without reading every sensitive discussion.

A Financial Services Cloud implementation should link tasks and goals to the correct individual or group, and test user access after an advisor reassignment. The workflow becomes useful when the next employee can understand the pending action without relying on informal email chains or notes kept outside the approved system.

Configure the Wealth Management Console

The Wealth Management Console is an advisor workspace built from the records and components already configured. It should follow the sequence of an advisor’s real work: find the client, confirm the household, review related accounts, prepare for a meeting, and record next steps. Adding every available panel can make those simple actions harder to complete.

The requirements are listed in Salesforce’s console prerequisites. They include Financial Account Management Standard Objects for the standard wealth console and specify administrator permissions. If a legacy managed-package console is installed, administrators must distinguish it from the standard app. Mixing the two experiences without reviewing their data models can confuse users.

Configure Pages Around Advisor Roles

Start with a household and an individual record page in a sandbox. Show the client’s assigned advisor, key relationships, and appropriate financial account summaries. Add Interaction Summaries or task lists where they help the team complete everyday work. Give client service associates the tools needed for service while restricting sensitive information to the people who are authorized to see it.

Salesforce Financial Services Cloud setup should verify page behavior with a normal advisor login. Test search results and related lists for both allowed and denied records. A dashboard that works under unrestricted access can fail as soon as it reaches a real service team.

Keep current figures and historical information visibly distinct. If an investment value was imported on a previous date, show enough source and timing context that users understand its limits. If an AI summary feature is licensed, test its source access separately; don’t assume the generated text respects every business convention simply because it appears inside Salesforce.

The console should be revised after advisor testing rather than built from a long wish list. A well-arranged page supports the firm’s processes, while accurate records and proper permissions provide the foundation for every component it displays.

Apply Security, Privacy, and Regulatory Controls

Financial firms handle nonpublic personal information and records that may be subject to regulatory preservation and supervisory rules. Security design needs to identify the applicable firm type and legal duties before configuring sharing, monitoring, and retention. A registered investment adviser, FINRA member broker-dealer, and dual registrant may have different obligations. The CRM vendor doesn’t decide those obligations for the firm.

The SEC outlines these duties in its Regulation S-P guidance, which explains the 2024 amendments addressing safeguards and incident response. Larger covered institutions had a December 3, 2025 compliance date, while smaller covered institutions had June 3, 2026. Both dates have passed as of October 2026. The rule’s requirements depend on the institution and information involved; enabling a Salesforce security feature doesn’t establish compliance by itself.

For FINRA member firms, the books and records rule requires preservation of specified records under applicable rules. FINRA Rule 3110 separately addresses supervisory systems and written procedures. Compliance staff should determine whether CRM notes, messages, or documents form part of regulated records and how they will be captured, retained, supervised, and produced.

Access Rules Must Reflect Real Advisor Relationships

Salesforce household management needs strict separation between relationship visibility and permission to view information. A member of a household isn’t automatically entitled to confidential notes, and one advisor’s household assignment doesn’t mean every regional employee should see the related balances. Test sharing at the object, field, and record levels. Document exceptions for supervisors and assistants rather than granting broad access to whole teams.

Test what happens when an advisor leaves and a book of business moves to another team. Ensure the authorized successor can work with the records while unnecessary access is removed.

For Salesforce for wealth management firms, security is also a question of which system holds a regulated copy. A document link in Salesforce doesn’t prove the underlying item satisfies retention or supervision rules. Confirm the approved archive and retrieval process with compliance and legal staff before launch.

Migrate Data, Test Relationships, and Plan the Rollout

Salesforce Financial Services Cloud setup should migrate records through the approved data model. A new org may import individual client accounts and groups before financial accounts, while an established package deployment needs mapping between its existing objects and the chosen target. Identify each data source’s owner and the date at which the extract was taken. Imports are safer when the same records can be traced back to those source identifiers.

The recommended order appears in Salesforce’s data load sequence, which recommends loading individuals and relationships before financial account transactions and holdings. It also warns against uploading transaction data that can interfere with calculated fields or rollups in relevant configurations. Use the sequence suited to the actual model and test it before a production cutover.

A Financial Services Cloud implementation should validate difficult cases rather than relying only on record counts. Create sample households with joint accounts, trust ownership, and multiple custodians. Reconcile their displayed totals to approved source figures. Test missing balances, duplicate imports, and account reassignment. Make the test accounts realistic without exposing live client information unnecessarily.

A wealth management CRM integration should be tested after credentials rotate and when an external endpoint is unavailable. Data owners must approve reconciliation results alongside the technical team.

After the wealth management CRM integration has passed acceptance tests, rollout can begin with a defined advisor group and then expand once the firm confirms the behavior of households and integrations. Financial Services Cloud implementation timelines differ greatly by legacy data and connected systems, so avoid promising a fixed number of weeks without discovery. Train advisors on both normal work and the correct response to inaccurate or missing financial information.

Understand Cost Drivers and Avoid Setup Mistakes

Licenses are only one part of project spending. Implementation work depends on whether the firm starts with clean records and an approved data model. A small advisory practice with one custodian may have fewer technical dependencies than a multi-office firm merging several systems.

Salesforce Financial Services Cloud setup costs rise when a firm must revise its client matching rules or rebuild integrations against standard objects. A fixed page count offers little insight into work involving complex client relationships.

Financial Services Cloud implementation mistakes often follow a familiar pattern. Teams enable a feature before deciding which records it should use. They treat household membership as legal account ownership, import balances without clear dates, or build workflows before compliance has reviewed their record requirements. The repair work can affect user access and reporting long after the original configuration is complete.

For Salesforce for wealth management firms, the practical budget should include licenses, implementation services, any custodian or data-provider subscriptions, testing, and ongoing administration. The first release should concentrate on a stable client identity, correct household relationships, useful advisor work, and source-verified financial information.

Conclusion: Build the Client Data Foundation First

Salesforce Financial Services Cloud setup works best when a firm decides how people, households, and financial accounts relate before creating the advisor interface. Current standard objects support many new implementations, while existing managed-package firms need to protect their data and integration dependencies. The custody system remains authoritative for the values it supplies, and access rules must reflect real responsibilities.

For Salesforce household management, correct membership and account roles prevent misleading relationship views. A well-designed wealth management CRM integration keeps outside values traceable and makes missing updates visible. The same care belongs in advisor workflows and regulated records. Those decisions give the firm a CRM it can operate and review, rather than a collection of pages that happen to display financial information.

Frequently Asked Questions

What Is Financial Services Cloud for Wealth Management?

It is Salesforce’s financial-services CRM offering with client relationship records, financial account structures, and advisor workflows. Firms can use it to organize households and display information from connected systems. Custody, trading, and detailed planning functions may continue in separate approved applications.

Is Financial Services Cloud Now Called Agentforce Financial Services?

Yes. Salesforce documentation now uses Agentforce Financial Services and notes that Financial Services Cloud may still appear in the product and help pages. The name change doesn’t make every AI feature part of an existing license. Check the exact contracted edition and any required add-ons.

How Should a Firm Begin Salesforce Financial Services Cloud Setup?

Start by identifying business users, source systems, and the existing Salesforce architecture. Choose a consistent financial services data model, confirm Person Accounts and permissions, and define account matching rules. Test the household and financial account records before configuring the advisor console.

Which Salesforce Licenses Do Wealth Advisors Need?

The right license depends on the tasks and features each person uses. Salesforce lists Financial Services Cloud Sales editions, with different included functions and limits. Advisors, service associates, and integration users may need different access arrangements. Confirm entitlements with Salesforce before allocating licenses.

How Much Does Financial Services Cloud Cost Per User?

Salesforce’s public US sales prices list Core at $325, Advanced at $500, and Max at $700 per user per month on annual billing. Those prices exclude implementation work and potential additional products. Contracts may differ from the public rates.

Should New Firms Use Standard Objects or the Managed Package?

Salesforce recommends core platform features for most new implementations. An existing managed-package firm should assess its integrations and customizations before changing object models. Don’t mix financial account objects from both architectures without a documented design and migration plan.

What Are Person Accounts in Financial Services Cloud?

Person Accounts represent an individual through an experience that combines account and contact fields. They’re the usual model for new financial services implementations. Existing firms may have an older individual model, which should be reviewed before any migration.

How Does Salesforce Household Management Work?

Salesforce household management connects people and related groups through relationship records. A household can include family members and related entities such as trusts. Membership should be kept separate from financial account ownership and permission to view confidential records.

What Is the Actionable Relationship Center?

The Actionable Relationship Center displays configured relationships between clients and related entities. It uses the underlying relationship records, so incorrect household or business links can produce an inaccurate graph. Set it up after client identities and relationships are verified.

How Are Investment Accounts Stored in Financial Services Cloud?

Standard objects can represent financial accounts, involved parties, balances, transactions, and other related information. A firm needs to map account identifiers and roles to the source records. Balance dates and household aggregation rules should also be checked.

Can Salesforce Connect to Custodians and Portfolio Systems?

Yes, through supported integrations and approved data feeds. Salesforce documents a BridgeFT connection for qualifying configurations, but that doesn’t cover every provider. A wealth management CRM integration requires matching rules, refresh schedules, error handling, and appropriate licensing.

Can Advisors Track Financial Plans and Goals in Salesforce?

Yes. Financial Plans and Financial Goals let firms record goals and related details using supported components. The firm must define which planning tool produces the underlying calculations. Recording a goal in CRM doesn’t by itself establish an approved financial recommendation.

Does Financial Services Cloud Ensure SEC and FINRA Compliance?

No. Salesforce provides controls and records that firms may configure for regulated work, but legal duties depend on the institution and its activities. Compliance staff must approve retention, supervision, privacy, incident response, and access practices. Product installation alone is insufficient.

How Long Does a Financial Services Cloud Implementation Take?

The timeline depends on legacy data, household complexity, integrations, and required reviews. A narrow setup can be shorter than a multi-custodian replacement program. Scope and test the source systems before committing to a launch schedule, and allow time for business and compliance acceptance.

What Must Be Tested Before a Wealth Management CRM Launch?

Test duplicate client handling, household membership, joint account totals, advisor permissions, and custodian feed failures. Confirm that financial values have known source dates and that confidential notes remain restricted. Business owners should accept the results before production access is expanded.