Historical data scope and migrate-versus-integrate decisions
Key Takeaway
Load lean: migrate only what business-critical operations need. Reach the rest where it lives through core banking integrations, real-time financial account information, or Data 360, instead of copying it into Salesforce.
When a financial institution moves to Agentforce Financial Services, a consultant decides which legacy data to load into Salesforce and which data to leave in source systems. Data left in source systems can still reach users through integrations or Data 360. The consultant also decides how to handle historical, rarely used data. The goal is a lean, accurate org that holds what business-critical operations need and keeps related records intact. A lean org also avoids copying large data sets that users can reach where they live.
Load lean
Loading lean means loading only the data and configuration your business-critical operations need, so the load disrupts those operations as little as possible. Loading lean is the best practice for both a large data volume (LDV) migration and ongoing large data syncs.
Storage cost is another reason to stay lean. You pay Salesforce for the storage your data uses. Exceeding your storage limits increases that cost, so data you load without a business need still costs money.