If an acquired company's ERP system will not be replaced immediately, what should the Architect recommend?

When an acquired company's ERP system will not be replaced immediately, utilizing nightly ETL (Extract, Transform, Load) batches for integration is a practical solution. This approach allows for the efficient transfer of data between systems on a scheduled basis, which can be beneficial when immediate real-time integration is not required or feasible.

Nightly ETL batches can handle large volumes of data in a controlled manner, minimizing the impact on system performance during business hours. This method also allows for complex data transformations and cleansing to ensure that the data is accurate and usable in the Salesforce environment.

Furthermore, using ETL for integration can help streamline the process of moving over historical data and regular updates from the ERP system without overwhelming both systems. This ensures that users have access to the latest information while maintaining the operational integrity of both systems until a more permanent solution can be implemented.

In contrast, building custom links for users may lead to a patchwork of integrations that can be labor-intensive and difficult to maintain. Leveraging real-time Apex callouts might introduce latency and performance issues, which can be problematic in a working environment. Utilizing an ESB for integration might be more complex and costly, especially if a simpler, scheduled batch process suffices for the organization's integration needs. Overall,