Skip to content
← Back to work
Case Study / Enterprise Billing Migration

Enterprise Billing Migration

Led billing migrations, coordinating cutover, validation, rollout sequencing and communications across business and technical teams.

Billing cutoverMigration validationCross-functional delivery

The work

At RealPage, I led billing migrations, coordinating cutover, validation, rollout sequencing and communications across business and technical teams.

Moving billing between platforms meant checking that contract data, product mappings and billing configuration produced the expected invoices. It also meant coordinating when customers moved and when teams communicated those changes.

CompanyRealPage
ResponsibilityBilling cutover, validation and rollout sequencing
ApproachPhased rollout aligned with billing cycles
CoordinationBusiness and technical teams

What I led

  • Validated billing setup before cutover, checking contract data, product mappings and expected invoices.
  • Sequenced rollout waves around billing cycles and outstanding dependencies.
  • Tracked readiness, issues and ownership in project plans, status updates and Azure DevOps.
  • Coordinated changes to migration dates and customer communications with participating teams.

How the rollout was organized

Billing validation and dependency tracking helped establish whether a wave was ready to move. Customer communications followed the rollout plan, including changes to that plan when readiness issues appeared.

Reconstructed rollout workflowAn illustration created for this case study from the work described here.

  1. Review billing inputs

    Contract data, product mappings and billing configuration.

  2. Validate invoices

    Compare expected invoices and identify discrepancies.

  3. Confirm readiness

    Review open issues, dependencies and billing-cycle timing.

  4. Cut over and review

    Coordinate the move and follow up on billing issues.

What readiness meant

Before a wave, I checked billing inputs and outstanding dependencies against the planned cutover. I documented issues and readiness requirements so the teams involved could work from the same plan.

Reconstructed readiness checklistThe checks are summarized for this case study; no project records or completion statuses are reproduced.
Billing inputs
Contract data, product mappings and billing configuration.
Invoice validation
Expected invoices and discrepancies requiring resolution.
Dependencies
Open issues, assigned owners and readiness requirements.
Rollout and communications
Billing-cycle timing, revised dates and customer notices.

A readiness decision

During a migration, billing errors increased after a rollout wave. I delayed the next wave, documented the revised date and rationale, and communicated the change before scheduled migration notices went out.

Cutovers had to align with billing cycles, so changing a date also meant revisiting the rollout sequence and dependencies.

Outcome

In that rollout, the delayed wave went live after the billing issues were resolved, and the broader migration completed.