Financial services implementations rarely fail on a feature. They fail on order: households designed before the client model is settled, rollups switched on during a bulk load, data sharing added after the data is already in. Pick a starting point, scope and complexity drivers, and get a six-phase sequence with dependencies, deliverables and exit gates.
This planner uses no customer data. It assembles public Salesforce documentation and delivery practice into a sequence. Steps tagged Documented come from the pages listed in the references. Steps tagged Practice are delivery recommendations, not vendor requirements. The product is documented as Agentforce Financial Services, formerly Financial Services Cloud, and names change between releases. Nothing here is regulatory or compliance advice, because requirements vary by jurisdiction and institution.
Starting point and scope
Starting point
Existing model means the individual model or the managed package financial account objects.
Scope
Households, relationships, financial accounts and rollups are always in scope.
Complexity drivers
Each one adds work to the sequence.
Your sequence
Order of the main workstreams
In a real environment
Data sources
The target org: installed packages, licenses, permission set licenses and the current client and financial account model.
Exports from core banking, wealth, insurance and CRM systems, with the keys that join them.
The institution's own access and conduct policies, written down before roles are designed.
For a migration, the existing individual-model or managed package records and their field mappings.
Limits and prerequisites
Users need both a permission set and a permission set license, and the available licenses depend on what was purchased.
Enabling person accounts needs specific permissions and editions: confirm in the target org.
Compliant Data Sharing documents a maximum of 10 active participant roles per enabled object. Confirm participant limits in the current admin guide.
Bulk loads run more slowly while rollups are enabled, and documented rollup limitations should be rechecked against current documentation.
How it would be validated
Reconcile household totals against the source systems for a labeled sample of clients.
Test access with real user profiles: each role sees what the policy allows and nothing more.
Rehearse the full load in a staging org and compare counts at every step.
Recalculate rollups after loads and compare the results with independent sums.
What this demo does not claim: durations, staffing, cost, success rates or readiness scores. It is not regulatory or compliance advice. It is a planning aid built from public documentation and delivery practice, and it does not replace a discovery of the actual org.