Skip to main content
Migration guide

Migrate to ERPClaw

Pick your source system. The AI agent handles the transcription. Most teams cut over in a weekend with a one-week parallel run. $0 forever after.

The migration approach

Every migration follows the same shape. Export from the source system. AI agent reads the export and runs ERPClaw's import actions to recreate the data. You spot-check trial balance and aging reports. Run parallel for a week. Cut over.

The AI piece matters. ERPClaw is AI-native: every action that creates a customer, posts a journal entry, or imports a transaction is callable from a chat agent. You don't write a migration script. You ask an agent to do the import, and it runs the right actions for your data.

The data integrity piece matters. ERPClaw enforces constitutional invariants at write time: double-entry balance, voucher balance, immutability of submitted GL entries, 23 invariant checks. If the source system had soft data corruption, the migration will surface it. That's a feature.

What the AI cannot do for you

  • ·Pick your chart of accounts. ERPClaw seeds a standard US GAAP chart; you decide whether to keep it or adapt yours.
  • ·Decide your fiscal year close date. ERPClaw asks; you answer.
  • ·Re-key custom integrations the AI can't reverse-engineer (rare, but happens with deeply customized SuiteScript on NetSuite).

Per-source guides on the way

We're shipping migration guides per source system based on real migrations we've helped run. If you're moving off something not on this list, open a GitHub issue and we'll prioritize.

Planned

From Sage Intacct

Mid-market financial SaaS

Planned

From Xero

SMB cloud accounting

Planned

From Odoo

Open-core ERP, Community or Enterprise

Planned

From ERPNext

Open-source ERP

Planned

From FreshBooks

Agency time-billing

Frequently asked questions

How long does an ERPClaw migration actually take?

From clean QBO export to ERPClaw running with the same data takes most teams a few hours of work spread across a weekend. The AI agent handles the transcription so you don't manually re-key journal entries. NetSuite migrations take longer because SuiteScript customizations have to be re-expressed as ERPClaw actions, but the AI assists that translation.

Will I lose my historical data?

No. The migration preserves your full transaction history. The agent imports chart of accounts, customers, vendors, items, and historical journal entries from your source system. You can run year-over-year comparison reports the day after migration. Your archived books in the source system stay readable for as long as that vendor lets you.

Do I need a developer or consultant to migrate?

Most teams self-migrate with an AI agent (Claude Code, Cursor, or similar) walking them through each step. ERPClaw has SKILL.md specs per module; the AI reads those plus your source export and runs the import actions. AvanSaber Inc. offers paid implementation services for teams that prefer not to self-host.

What happens during the migration weekend?

Friday: install ERPClaw on your hardware, export from your source system. Saturday: AI agent transcribes the data, you spot-check the trial balance and AR/AP aging against the source. Sunday: parallel run for one week to catch any reconciliation gaps. Monday following: cut over fully. No firm needs a 6-month consulting engagement.

What's the cost of migrating off SaaS to self-hosted ERPClaw?

Software cost: $0 forever. Server cost: your choice ($0 if you self-host on existing hardware, $5 to $20 per month for a VPS if you prefer cloud). Implementation: $0 if you self-migrate with an AI agent, or paid services from AvanSaber Inc. if you want managed help. Compare that to the all-in cost of staying on your current SaaS stack.

Related: read the AI-native ERP framework, the 13-vendor matrix, the pricing page ($0 forever), or per-source comparisons at /compare/quickbooks/ and /compare/netsuite/.