We implemented Claw's billing module three months ago to replace a patchwork of spreadsheets and Stripe Billing. The migration went okay, but we've hit a hard blocker.
Our new enterprise contracts require multi-currency invoicing (USD, EUR, GBP) with fixed exchange rates per contract. Claw's module treats all transactions in the tenant's base currency only. Their support says this feature isn't on the roadmap.
We're now in a situation where we can't invoice these new clients correctly. The forcing function is clear: we need to fix this fast.
Our current thinking is to rollback to Stripe Billing while we evaluate other platforms like Orb or Workbooks. But we've already migrated a quarter of our customers onto Claw.
Has anyone managed a partial rollback of a billing system? Specifically:
- How did you sequence moving customers back without double-billing?
- Did you keep any migrated data in Claw, or was a full extract necessary?
- Where would we likely slip up? Our main fear is missing invoicing cycles.
We're a small team, so a full rebuild now is daunting, but the contract issue is a showstopper.
Multi-currency being "not on the roadmap" after you've migrated in is classic. Their sales deck probably showed a globe icon, didn't it?
A partial rollback is messy, but doable. Start by freezing all new customer migrations and new invoice runs in Claw immediately. For the sequence, you move customers back in reverse order of their billing date - the ones who just got invoiced stay in Claw until their next cycle, the ones furthest out get moved first. This avoids double-billing but stretches the pain.
Your main slip-up won't be the invoicing cycles, it'll be the prorations and credit balances. Claw's data model for those is never what you think it is. Do a full extract, but assume you'll be manually reconciling for months. Good luck.
Your stack is too complicated.
Oof, multi-currency with fixed rates is a killer. That "not on the roadmap" response is them politely telling you to walk.
You're right to freeze everything in Claw. For the sequencing, don't just go by billing date, go by contract *type*. Move all your new multi-currency clients back first, as a bloc. They're the immediate fire. Your legacy single-currency customers in Claw can stay put as a holding pattern, it's less risky than moving everyone at once.
The slip-up won't be the invoice cycles, you can lock those. It'll be the webhook integrations and provisioning logic that now point to Claw. Did you tie entitlements or feature flags to invoice status? That's where the real chaos lives. You'll be finding broken links for weeks.
And do a full extract, but archive it. You'll never fully trust it. Manual reconciliation is inevitable, so just budget the hours now. Seen this movie before.