Free Access Salesforce AP-223 New Release

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.

Setting Legal Entity on:

Order Product

Order Product Consumption Schedule

Must be scalable, bulk-safe, and future-proof.

The most performant and Salesforce-recommended approach is:

No additional DML required

Runs before insert and update

Bulk-safe

Better performance than Workflow or Process Builder

No need to use QCP, which only affects Quotes—not Orders or Schedules

✔ Before-Save Flow (Record-Triggered Flow)Thus D is correct.

The three customer teams that must be involved in Revenue Cloud scoping are:

✔ A — Information (Product / Pricing owners)They define product catalog rules, pricing models, and offerings.

✔ B — Technology (IT/Architecture)Ensures integration, data migration, security, and platform alignment.

✔ C — Sales OperationsOwns quoting flows, approvals, discounting, sales motions, and user experience.

These teams define core CPQ processes.

Why others aren't required at scoping:Team

Why Not Required

D — Accounting/Finance

Essential for Billing scoping, but not required for CPQ-only scoping unless Billing is in scope.

E — Customer Service

Usually relevant for Service Cloud and CALM, not initial CPQ scoping.

F — Human Resources

Irrelevant to CPQ and Billing.

Thus A, B, C is correct.