Implementation
Importing Existing Credit Balances Without Losing Their History
By the Orvlin team · · 1 min read
Credit balance migration: what to decide
A customer’s 10,000 credits contain a paid pack and a restricted promotion. The new system imports all 10,000 as unrestricted purchased credits. The total matches, but the commercial promise has changed.
Reconcile opening balances to the old ledger and specify the cutover time. Preserve sufficient history to explain the opening amount. Freeze or coordinate writes so usage during migration is not missed or counted in both systems.
A concrete scenario
An account has 6,000 purchased credits and 4,000 promotional credits expiring Friday. Two opening grants preserve that distinction. One undated 10,000-credit grant does not.
A detail teams often miss
Pending reservations matter too. If an in-flight job has reserved 500 credits, importing the spendable total without the reservation can allow another job to spend the same capacity.
Before you put this into production
- Export balances and grant metadata.
- Choose a clear cutover timestamp.
- Carry pending reservations or settle them explicitly.
- Reconcile per-account opening and closing totals.
Frequently asked questions
- Do we need every historic ledger row?
- Not necessarily in the active system, but retain accessible evidence for the opening balance and preserve restrictions that still affect the customer.