Short answer
Migrating from Ebix SmartOffice to Salesforce Financial Services Cloud moves contacts, households, policies, accounts and activity history into FSC, giving insurance and wealth firms a modern platform for service, marketing and integrations.
Why firms make this move
SmartOffice has long served insurance and financial advisors. Firms move to Salesforce when they need better automation, integration with carriers, custodians and marketing tools, and reporting across advisors. Policy and account data needs careful mapping to FSC financial accounts or insurance policy objects.
What moves
- Contacts and households
- Policies and financial accounts
- Activities, notes and documents
- Agent and advisor assignments
How the data maps
| From | To |
|---|---|
| Contact | Person account |
| Household | Household account |
| Policy | Insurance policy or financial account |
| Activity | Task or event |
| Agent | User or producer record |
What to watch out for
- Policy data that should come from carrier feeds instead
- Duplicate contacts across agents
- Document volume and storage
How Vantage Point runs the migration
- Discovery and data inventory: what exists, what is clean, what is worth moving
- Target design: objects, record types, households or companies, ownership and security
- Field-by-field data mapping document, signed off by business owners
- Cleanup and deduplication before the move, not after
- Test loads into a sandbox with reconciliation reports
- User acceptance testing with real scenarios
- Cutover: final delta load, integrations switched, old system set to read-only
- Hypercare and adoption support
Typical timeline
Typically 6 to 12 weeks.
Frequently asked questions
Can policy data come from carriers instead of the export?
Often it should, because carrier or agency feeds stay current while an export is a snapshot.
Do we keep agent ownership?
Yes. Agents and advisors are mapped to Salesforce users so records keep their owners.