These are the three factors that increase scope during legacy data migration for Revenue Cloud:
✔ A — Extracting from multiple sources takes more time and resourcesIf legacy data is spread across multiple CRMs, ERPs, billing engines, or flat files, this increases:
Extraction complexity
Mapping effort
Data cleansing time
This always expands project scope.
✔ B — Fragmented or incomplete information must be aggregated and validatedIf legacy data is dirty or inconsistent:
Amendments fail
Renewals break
CPQ calculations are wrong
Billing proration becomes inaccurate
Data validation + cleanup = additional scope.
✔ D — Large data volumes take longer to loadFull loads of:
Order Products
Subscriptions
Assets
Contracts
…can take hours to days, requiring:
Batch loading
Testing
Restart planning
Performance tuning
This clearly expands scope.
Why C and E are not correct:Option
Reason
C — External objects eliminate migration
Completely false. CPQ/Billing cannot use external objects for core processes such as pricing, contracting, amendments, renewals, invoicing.
E — Amendments/Renewals require customizations
Not a migration consideration; it is a design topic, not a factor that expands migration scope.
