Plan your go-live
Plan your go-live
Plan your go-live
Before you start billing customers, validate your setup, decide on a deployment strategy, and prepare for the cutover. This page covers the technical and operational decisions.
Once your meters, products, pricing plans, and subscriptions are set up, test them end-to-end before going live.
Create test subscriptions — Set up subscriptions with real pricing and customer data (use test customer records). Send usage events matching your production patterns and review the generated draft invoices.
Compare against your current system — Export the draft invoices from Solvimon and compare them line-by-line against what your current billing system would generate. Look for:
Check the data pipeline — If you’re ingesting usage from an external system, run a full dry-run of that integration. Verify that events arrive in Solvimon with the correct customer reference, meter reference, and timestamp.
See the report downloads guide for export options.
There are two main approaches. Choose based on pricing complexity, data migration scope, and risk tolerance.
Soft launch — Start with a subset of customers (e.g., new signups, a pilot account, or one business unit). Let them bill for 1–2 cycles while your current system continues as the source of truth. Once you’re confident, expand to more customers. This reduces immediate impact if something breaks, but requires running two systems in parallel for longer.
Full cutover — Migrate all customers at once on a specific date. Requires more upfront validation but reduces long-term complexity. Choose a date that gives your finance team time to close the previous period in the old system.
Pick your cutover date — Align with your billing cycle. If you bill monthly on the 1st, cutting over on the 1st of a month is cleanest. Make sure your team is available to monitor during and after the cutover.
Prepare your integration — If you’re ingesting usage via API, have your logging and monitoring ready. Set up alerts for failed event ingestion or missing events. Test your backfill process (if needed) before the actual cutover.
Plan for rollback — Decide: if something goes wrong, can you roll back to your old system? For how long? Have a clear decision tree for what triggers a rollback vs. a fix-forward approach.
Communicate the timeline — Give your team, customers (if relevant), and stakeholders clear notice of the cutover date and expected impact.
If you’re migrating from an existing billing system, you may need to backfill historical usage or import existing subscriptions. See Backfill and migrate usage data for the available import methods.
Timeline varies widely based on pricing complexity and data migration scope.