Managed package to standard data model migration planning
Key Takeaway
Test the metadata and data migration thoroughly in a sandbox, then switch the whole org to the standard objects together instead of mixing package and standard objects. When you load data, load Financial Account records before the records that point to them, such as Financial Account Party and Financial Account Address.
Agentforce Financial Services can store financial data in two ways: an older managed package with its own custom objects and fields, or a newer set of standard objects built into the platform. Migration planning means deciding whether to move from the package to the standard data model, mapping objects and fields between the two, and moving metadata and data without breaking relationships or dependent apps. The standard data model splits some package fields into separate related objects, so the order of your data loads decides whether each record can find its parent.
The two data models
The managed package adds its own components to the org: custom fields, permission sets, profiles, layouts, triggers, and custom settings. The standard data model uses platform objects instead, so features such as Financial Account and Groups and Households work without installing the managed package.
Some package custom fields are now standard, but many package components are unique to the package. Any package component without a standard equivalent must be recreated during customization.
Many features exist in both data models, but not all of them. The table shows examples of where features are available.
| Example features | |
|---|---|
| In both data models | Group Membership and Households, Financial Account and related objects, Financial Holdings, Goals, Record Rollups |
| Only in the managed package | Referrals, and reports such as Advisor Reports and Top Referrals |
| Only partly available as standard features | CRMA Analytics Templates, the Household API, the Data 360 for FSC Data Kit |