Document the pattern and technical approach we used previously for successful, outage-free migration of the billable_usage_remittance database table. This documentation should detail how we used an approach of using an API instead of our usual liquibase changeset to achieve this.

This will serve as our current accepted pattern for changes like SWATCH-3478.

Acceptance Criteria:

• Create an InScope document that curates this as the process we use for this kind of large database migration
• Share the document with the team