FSC Household Management Best Practices | Vantage Point

Introduction

If you're a financial advisor managing a high-net-worth family, you don't just manage one person — you manage an entire ecosystem. There are spouses, dependents, trusts, business entities, attorneys, CPAs, and extended family members, all with interconnected financial lives.

Yet most CRM systems treat each person as an isolated record. That's a problem.

Salesforce Financial Services Cloud (FSC) solves this with household management — a powerful framework that groups related individuals and entities into unified views, giving advisors a comprehensive picture of every client relationship they serve.

But here's the challenge: household management is one of the most strategically important — and most commonly misconfigured — features of FSC. Done right, it transforms how your firm serves clients. Done wrong, it creates data chaos, adoption resistance, and compliance blind spots.

This guide covers everything you need to know about FSC household management best practices, from technical architecture and rollup configuration to data migration, compliance, and real-world implementation strategies.

What Is a Household in Salesforce Financial Services Cloud?

A household in Salesforce FSC is a structured grouping of individuals and related entities whose relationships and shared attributes define how your firm serves them. Unlike traditional CRM systems that treat each customer as a standalone record, FSC households capture the full spectrum of relationships — spouses, dependents, trusts, business entities, and professional advisors — all connected through a sophisticated data model.

How Households Work Technically

At the core of FSC's household architecture is the Party Relationship Group object. This model integrates several interconnected components:

• Business Accounts — Represent the household entity itself
• Person Accounts — Capture individual family members
• Account-Contact Relationships — Link individuals to household accounts
• Contact-Contact Relationships — Map interpersonal connections (spouse, parent-child, attorney-client)
• Account-Account Relationships — Define connections between business entities, trusts, and households

A business account is classified as a household (rather than a business) because it's related to a Party Relationship Group with the type "Household." This multi-layered data model lets advisors navigate seamlessly from an individual client record to the entire household's financial landscape.

Why Households Matter for Financial Services

A Forrester Total Economic Impact study found that FSC implementations delivered $81.3 million in total benefits over three years — and household management was a central driver.

Best Practice #1: Define Your Household Strategy Before You Build

Should You Enforce Households?

One of the most critical decisions you'll make is whether to enforce household assignment for every client or leave it optional. Here's how to think about it:

Enforce households when:

• Your firm primarily serves wealth management or multi-member financial planning clients
• You need consistent reporting across all client segments
• You plan to integrate Salesforce with portfolio management platforms that require household grouping (e.g., Orion, Black Diamond, Tamarac)
• Compliance requires tracking family-level relationships and shared accounts

Consider making households optional when:

• You serve a mix of individual and household-oriented clients
• Some client segments (young professionals, individual retirees) don't benefit from household structure
• Your advisors are transitioning from a system that didn't use households, and you want to ease adoption

Hybrid approaches that work well:

• Enforce households only when prospects convert to clients
• Enforce households for specific client segments (e.g., clients with $500K+ AUM)
• Automate household creation through flows to reduce manual effort

Define Household Roles and Relationship Types

Before configuring households, map out the roles and relationships your firm needs to track:

Standard roles to consider:

• Primary Decision Maker
• Spouse / Partner
• Dependent / Minor Child
• Trustee / Beneficiary
• Power of Attorney
• Legal Counsel
• CPA / Tax Advisor

Custom roles for specific segments:

• Trust Administrator (for estate planning firms)
• Corporate Officer (for institutional clients)
• Family Office Manager (for UHNW families)

Best Practice: Create a governance process for adding new roles. Without controls, you'll end up with duplicative or conflicting relationship types that undermine data quality.

Best Practice #2: Get Your Data Architecture Right

Naming Conventions

Establish consistent naming conventions for household accounts before creating a single record:

• Format: [Last Name] Household or [Last Name] Family Household
• Multi-surname families: [Name1]-[Name2] Household
• Business-linked households: [Last Name] Household (linked to [Business Name])

Validation rules can enforce these conventions automatically.

Primary Group Assignment

Each person account can belong to multiple Party Relationship Groups (households, trade associations, boards) but can only have one primary group. Best practices:

• Set the primary household as the default primary group
• Configure automation to flag records without a primary group
• Create exception handling for individuals who may legitimately not belong to a household

Record Type Configuration

Best Practice #3: Configure Rollup Fields for Maximum Visibility

One of FSC's most powerful household features is automatic rollup functionality, which aggregates financial data across all household members. Properly configured rollups give advisors instant visibility into the household's complete financial picture.

Key Rollup Metrics to Configure

How to Set Up Record Rollup Definitions

FSC uses Record Rollup Definitions and the Data Processing Engine to calculate financial summaries. Here's the recommended configuration approach:

1. Define aggregation rules — Specify which financial accounts to include (e.g., only active accounts, exclude closed positions)
2. Set rollup scope — Choose whether to roll up from individual members only or include related entities like trusts
3. Configure financial summary rollups — Use FSC's eight predefined Data Processing Engine definitions for investments, liabilities, and bank deposits
4. Test with real data — Validate rollup accuracy against known client portfolios before going live
5. Schedule refresh cadence — Set automated rollup recalculation schedules (daily for AUM, weekly for less volatile metrics)

Common Pitfall: Rolling up data from inactive or closed accounts inflates household totals. Always configure filters to include only active financial accounts in your rollup definitions.

Best Practice #4: Leverage the Actionable Relationship Center (ARC)

The Actionable Relationship Center (ARC) is FSC's visual relationship mapping tool, and it's a game-changer for household management. ARC transforms complex relationship data into interactive graphs that advisors can navigate intuitively.

What ARC Visualizes

• Family structures and decision-making hierarchies
• Connections between households, trusts, and business entities
• Professional relationships (attorneys, CPAs, insurance agents)
• Extended network and referral opportunities
• Risk concentrations across related entities

ARC Configuration Best Practices

1. Customize the Household Graph template — FSC includes a preconfigured Household Graph. Extend it to show the nodes most relevant to your firm (e.g., trust entities, referral sources).
2. Enable inline editing — Allow advisors to create and update relationships directly from the ARC visualization, reducing data entry friction.
3. Add ARC to key page layouts — Include the Relationship Graph component on Person Account, Household Account, and Opportunity record pages.
4. Create role-specific ARC views:
   • Wealth advisors: Focus on financial accounts, trusts, and household members
   • Service teams: Emphasize recent interactions, open cases, and service preferences
   • Marketing teams: Highlight referral networks and campaign engagement
5. Train advisors on ARC navigation — ARC is only valuable if advisors actually use it. Include hands-on ARC training in every FSC onboarding program.

Best Practice #5: Plan Your Data Migration Carefully

Data migration is often the most complex — and most underestimated — aspect of household implementation. Most firms are migrating from systems that didn't have a household concept, which means relationships must be inferred, validated, and built from scratch.

Migration Phases

Phase 1: Data Audit and Cleansing

• Identify existing relationship data across all source systems
• Resolve duplicate records before migration
• Standardize naming conventions
• Flag incomplete or inconsistent relationship data

Phase 2: Relationship Mapping

• Define rules for inferring household relationships (e.g., matching last names and addresses)
• Create mapping documents for each data source
• Validate inferred relationships with advisors
• Handle edge cases (blended families, individuals in multiple households)

Phase 3: Staged Migration

1. Migrate Person Accounts first
2. Create Household Business Accounts
3. Establish Account-Contact Relationships
4. Build Contact-Contact Relationships (spouse, dependent, etc.)
5. Link financial accounts and assets
6. Run rollup calculations and validate totals

Phase 4: Validation and Reconciliation

• Compare household AUM totals against source systems
• Verify relationship types and roles
• Conduct advisor spot-checks on migrated households
• Run data quality reports and resolve discrepancies

Pro Tip: Use an incremental migration approach — migrate a pilot group of 50–100 households first, validate thoroughly, then proceed with the full migration. This catches data quality issues early before they multiply.

Best Practice #6: Build for Compliance and Security

Regulatory Alignment

Household management must comply with financial services regulations including SEC, FINRA, GLBA, and state-specific privacy laws. FSC provides built-in features to support compliance:

• Audit trails — Every household modification is logged, including member additions, role changes, and relationship updates
• Data retention policies — Configure retention rules aligned with your firm's regulatory obligations
• Consent management — Track and enforce communication consent at the individual and household level
• Compliant Data Sharing — FSC's built-in framework for sharing data across household members while respecting individual consent

Security Model Design

Design your sharing model carefully to balance advisor access with privacy protections:

• Advisor access: Full read/write on primary client records; configurable access to spouse and dependent records based on documented consent
• Team access: Service team members may need read-only access to household records for case resolution
• Sharing rules: Use household-specific sharing rules to grant team-level access without overexposing data
• Permission sets: Create FSC-specific permission sets for different user roles (advisor, service rep, compliance officer)

Best Practice for HIPAA-adjacent firms: If you serve clients in healthcare or insurance verticals, layer additional field-level security on sensitive data fields within household records.

Best Practice #7: Integrate Households Across the Salesforce Ecosystem

Service Cloud Integration

With Service Cloud integrated, support agents gain full household context:

• View all household members' recent cases and interactions
• See shared service preferences across the household
• Access pending service requests for any family member
• Route complex inquiries to the advisor who manages the household

Marketing Cloud Synergy

Household-level marketing unlocks powerful campaign strategies:

• Life event targeting — Trigger campaigns when household data indicates life events (new baby, retirement, inheritance)
• Multi-generational outreach — Engage multiple generations within affluent families
• Coordinated messaging — Ensure consistent communication across household members
• Referral campaigns — Leverage extended networks mapped in ARC

Data Cloud and AI

Integration with Salesforce Data Cloud and Einstein enables advanced household analytics:

• Cross-sell scoring — AI-driven recommendations based on household financial profiles
• Attrition risk — Predict which households are at risk of leaving based on engagement patterns
• Life event prediction — Machine learning models that anticipate major financial events
• Portfolio optimization — Household-level investment recommendations

MuleSoft Integration

For firms with complex technology stacks, MuleSoft enables real-time data synchronization between FSC households and:

• Portfolio management platforms (Orion, Black Diamond, Tamarac)
• Financial planning software (MoneyGuidePro, eMoney)
• Custodian platforms (Schwab, Fidelity, Pershing)
• Document management systems (DocuSign, Laserfiche)

Common Mistakes to Avoid

Based on hundreds of FSC implementations, here are the most frequent household management mistakes:

1. Skipping the strategy phase — Jumping into configuration without defining household policies, roles, and naming conventions
2. Ignoring data quality — Migrating dirty data creates corrupted households that erode advisor trust
3. Over-complicating roles — Creating too many relationship types makes data entry burdensome and inconsistent
4. Forgetting change management — Advisors accustomed to individual-focused CRMs need training and support to adopt household-centric workflows
5. Neglecting rollup validation — Incorrect rollup configurations produce inaccurate financial summaries that undermine the entire system
6. Not planning for edge cases — Blended families, individuals in multiple households, and trust-heavy estates require thoughtful configuration
7. Treating households as static — Family structures change. Build workflows to update households when life events occur (marriage, divorce, death, new dependents)

Implementation Roadmap: A Phased Approach

Phase 1: Foundation (Weeks 1–4)

• Define household strategy and enforcement rules
• Design data architecture and naming conventions
• Configure record types, roles, and relationship types
• Set up validation rules and automation

Phase 2: Core Configuration (Weeks 5–8)

• Configure rollup fields and Data Processing Engine definitions
• Set up ARC visualization templates
• Design page layouts for household and individual views
• Build sharing rules and permission sets

Phase 3: Data Migration (Weeks 9–14)

• Execute data audit and cleansing
• Run pilot migration (50–100 households)
• Validate and reconcile
• Complete full migration

Phase 4: Integration (Weeks 15–18)

• Connect portfolio management platforms
• Configure Marketing Cloud household segments
• Enable Data Cloud analytics
• Test end-to-end workflows

Phase 5: Adoption (Weeks 19–24)

• Conduct advisor training programs
• Launch with pilot advisor group
• Gather feedback and iterate
• Roll out to full organization

FAQ: FSC Household Management

What is the difference between a household and a group in FSC?

A household is a specific type of Party Relationship Group designed for family units sharing financial interests. A group is a broader concept that can represent any collection of related individuals — trade associations, corporate boards, neighborhoods, or custom groupings. Both use the Party Relationship Group object, but with different type classifications.

Can a person belong to multiple households?

Yes. A person account can be a member of multiple Party Relationship Groups, including multiple households. However, each person can only have one primary group. This is common for individuals who belong to both their nuclear family household and an extended family estate planning group.

How do rollup fields handle inactive accounts?

By default, rollup definitions should be configured with filters to exclude inactive or closed financial accounts. If not properly configured, rollups will include all linked accounts, potentially inflating household totals. Always specify activation status filters in your Record Rollup Definitions.

What happens to a household when a member leaves (divorce, death)?

FSC provides workflow tools to manage household changes. When a member leaves, you can deactivate their Account-Contact Relationship with the household, create a new household for them if needed, and update rollup calculations. Best practice is to build automation that guides advisors through these transitions.

Is household data visible in reports and dashboards?

Yes. Because households are represented as business accounts, they can be used in standard Salesforce reports and dashboards. You can create household-level reports showing AUM by household, revenue by household tier, and household engagement metrics.

How does FSC household management compare to the managed package version?

FSC offers two approaches: the core platform model (using Party Relationship Groups) and the older managed package model. The core platform model is the recommended approach for new implementations as it uses standard Salesforce objects and provides greater flexibility. The managed package model uses custom objects and is primarily maintained for legacy implementations.

Can I automate household creation?

Yes. You can use Salesforce Flows to automate household creation — for example, automatically creating a household when a prospect converts to a client, or when a new person account is created with a matching last name and address as an existing client. The New Group flow in FSC provides a guided experience for manual household creation.

Conclusion

FSC household management isn't just a feature — it's a strategic capability that transforms how financial services firms understand and serve their clients. When implemented correctly, it drives measurable outcomes: higher revenue through cross-selling, faster service delivery, stronger compliance postures, and deeper client relationships that span generations.

The key to success is treating household management as a business initiative, not just a technology configuration. Start with clear strategy, invest in data quality, train your advisors, and iterate based on real-world usage.

Ready to transform your firm's client relationship management? Vantage Point specializes in Salesforce Financial Services Cloud implementations for wealth management firms, RIAs, banks, and insurance companies. Our team has deep expertise in household management configuration, data migration, and advisor adoption strategies.

Contact Vantage Point to discuss how we can help you get the most from FSC household management.

About Vantage Point

Vantage Point helps regulated industries — including wealth management, banking, insurance, healthcare, and fintech — unlock the full potential of Salesforce, HubSpot, MuleSoft, and Data Cloud. From implementation and integration to AI-powered personalization, we help firms modernize their client engagement strategies and drive measurable growth. Learn more at vantagepoint.io.