Post Data Migration UAT Plan Guidance

Catalogue

Plans, add-ons, discounts, coupons, price lists

Existence, names, amounts, handles

Customers

Customer records (and optionally active-only)

Count, key fields, handles

Payment methods

Payment methods linked to customers

Present where expected, usable

Subscriptions

Active contracts as subscriptions

Plan, customer, state, dates, add-ons, discounts

1.1

In Billing, list plans (API or Dashboard).

Number of plans matches (or is within expected range of) migration report.

1.2

For 2–3 plan names you know from Transform, find them in Billing by name or handle.

Same plan names exist; handle format is string (e.g. prefixed).

1.3

Open one plan and check amount, interval, and currency.

Matches the plan in Transform (or your source list).

2.1

In Billing, list add-ons.

Count aligns with migrated components from migration report.

2.2

For 2–3 add-ons you know from Transform, find them in Billing.

Names/handles match; pricing matches where applicable.

3.1

In Billing, list discounts.

Count aligns with migration report.

3.2

For 1–2 discounts you know from Transform, check handle and amount/percentage.

Correct type (amount/percentage) and value.

4.1

In Billing, list coupons.

Count aligns with migration report (if coupons were migrated).

4.2

For one coupon you know from Transform, verify code and validity.

Coupon exists and state is as expected.

5.1

In Billing, list price lists.

Count aligns with migration report.

5.2

Spot-check one price list: name and that it is attached to expected plans/products where applicable.

Consistent with Transform.

6.1

In Billing, list customers (or filter by a known handle pattern).

Total count matches (or is within expected range of) migration report.

6.2

For 3–5 sample customers, open each in Billing and verify: email, name, company, address, country.

Data matches Transform (or source export).

6.3

Note the Billing handle for each sample customer.

Handles are strings; you can use them for subscription lookups.

7.1

For 2–3 sample customers who had payment methods in Transform, check in Billing that the customer has at least one payment method.

Payment method(s) exist for those customers.

7.2

If possible, check type (e.g. card) and last4/masked number.

Consistent with what you had in Transform (no full PAN).

8.1

In Billing, list subscriptions; filter by state active (and on_hold if you use it).

Count of active (and on_hold) subscriptions aligns with migration report.

8.2

For 3–5 sample subscriptions (by customer name or subscription handle), open each and verify: plan, customer, start date, next billing date, state.

Matches the contract in Transform.

8.3

For subscriptions that had add-ons in Transform, open the same subscription in Billing and check add-ons.

Same add-ons attached; quantities correct.

8.4

For subscriptions that had discounts in Transform, check discount(s) on the subscription in Billing.

Same discounts applied.

8.5

For one subscription, check currency and amount (plan + add-ons).

Matches expected recurring amount.

9.1

In Billing, list dunning plans.

Expected dunning plan(s) exist.

9.2

If subscriptions are linked to a dunning plan, spot-check one subscription.

Dunning plan assignment is correct.

O.1

Create a test subscription in Billing for a test customer (using a migrated plan and add-on).

Subscription is created and appears in list; first invoice (if applicable) is created.

O.2

If you use Billing’s customer portal or checkout, log in or complete a test flow with a migrated customer.

Customer can be identified; no errors due to missing data.

O.3

If you have webhooks configured in Billing, trigger one event (e.g. invoice settled) and confirm your endpoint receives the event.

Webhook delivered; payload contains expected handles (customer, subscription, invoice).

UAT lead

Business / product