Short answer
Map every Redtail or Wealthbox contact type to an FSC record type first: people become Person Accounts, families become households, and businesses and trusts become their own Accounts linked through relationships. List every source field and every picklist value, even the ones you won't migrate, and validate the load against a full export, not a sample.
Map the record types first
| Source record | Financial Services Cloud target |
|---|---|
| Individual contact | Person Account |
| Household or family | Household Account, with members linked through Account Contact Relationships |
| Company, trust or other entity | Business Account, related to people with roles |
| Relationships between contacts | Account Contact Relationships or Contact Contact Relationships, with a role on each |
| Accounts and holdings | Financial Accounts and Financial Account Roles, usually fed by the custodian or portfolio system |
| Activities and notes | Tasks, Events and Notes, linked to the person and the household |
| Workflows | Action Plans or Flow, or archived if nobody uses them |
Build the inventory before the mapping
- Every source field, including the ones you decide not to migrate. Clients ask later where a field went, and "not migrated, by decision on this date" is a good answer.
- Every distinct picklist value, with its target value. Free-text categories in the old CRM often hold dozens of spellings of the same thing.
- An owner crosswalk from old CRM users to Salesforce users, including people who have left.
- Custom fields and tags, with a decision for each: field, picklist value, campaign membership or drop.
Load and validate
- Load households, then people, then relationships, then financial accounts, then activities.
- Keep the Redtail or Wealthbox ID in an external ID field on every record.
- Validate against the full export, not a 50-record sample. Matching problems, especially duplicate email addresses across family members, only show up at full volume.
- Re-run the validation against an older backup as well. It catches fields the mapping missed.
- Cut over with a full load followed by a delta for changes made during the freeze.
Watch for
- Spouses who share one email address. Decide which person owns it before you load, or duplicate rules will block one of them.
- Documents. Most firms keep files in their document system and link them from Salesforce instead of migrating the files themselves.
- Workflows nobody runs any more. Retire them instead of rebuilding them.
Official documentation
Frequently asked questions
What does a Wealthbox household become in Financial Services Cloud?
A Household Account. Each member is migrated as a Person Account and linked to the household through an Account Contact Relationship that carries their role and the primary group flag.
Do Redtail workflows migrate to Salesforce?
Not automatically. Rebuild the ones the team still uses as Action Plans or Flow, and archive the rest. A migration is a good time to retire workflows nobody runs.
Salesforce, HubSpot, Anthropic and OpenAI change their products often. Check the official documentation before you rely on a specific setting, limit or price.