Legacy system landscape assessment and source-to-target mapping
Key Takeaway
Know where client and financial data lives today and where each piece belongs in one target model. An org that already uses the managed package financial account objects first plans the metadata and data migration of those records, using the API name mapping. In the standard model, owners and balances become their own records instead of fields.
A data migration into Agentforce Financial Services starts with an assessment of where client and financial data lives today and where each piece belongs in the new data model. Source-to-target mapping turns that assessment into object and field decisions, plus the order in which data is loaded. For example, it decides how managed package financial account fields move into the standard Financial Account, Financial Account Party, and Financial Account Balance objects. Careful mapping and load order keep loads accurate and keep related records correctly linked.
Assess the legacy sources
Client and financial data usually comes from many systems. Common sources are custodians, banking systems, financial planning, portfolio management, asset aggregation, and the other platforms that support the front to back office. Integrating data from these systems is a major implementation task.
Not every legacy source needs a one-time copy. Integrations can populate and update Financial Account and Financial Account Transaction with real-time data from core banking systems. Data 360 makes data available to Salesforce without copying it, which can avoid the expense of a massive data migration project.
An integration user can move data from external systems into Financial Account and related objects through the API without extra Agentforce Financial Services licenses. To grant the needed object permissions, update the integration user's permission set license.