Universal container (UC) is implementing communication cloud and the business is asking a consultant to...

Migrating millions of historical orders creates a large-data-volume footprint that can reduce query and reporting performance and can force the target org to preserve historical catalog dependencies, including products that are no longer sold. For future service management, the customer ' s current Assets generally provide more direct operational value because they are the state used for subsequent MACD activity. The recommended configuration follows the native Communications Cloud responsibility boundary: catalog and CPQ determine the commercial request, while Order Management, OmniStudio, or the relevant platform service performs the downstream processing required by the use case. A large record count does not guarantee that Order Management will fail; Salesforce can support large datasets when architecture, indexing, loading, and retention are designed correctly. The key design decision is whether the historical transaction detail provides enough business value to justify its storage and catalog dependencies. Avoiding duplicate logic is important because repeated rules across catalog, integration, and orchestration layers quickly become inconsistent as products evolve. The selected approach keeps the authoritative data in the correct object model, supports later lifecycle operations, and minimizes additional processing or manual intervention. It should be implemented declaratively wherever the platform feature can express the requirement, with customization reserved only for behavior that genuinely falls outside the supported framework.

Study Guide Reference:Large data volumes; historical-order migration; asset migration; catalog dependencies; lean data strategy.