Migration guide
Move from Wave to Invoice Crowd with complete exports, normalized customer and document files, test imports, and a balanced cutover.
Last updated:
Safe cutover
Invoice Crowd may fit a service business that wants proposals, purchasing, projects, time, multi-business profiles and broader payment choices. Wave remains attractive to eligible US and Canadian businesses that want its Starter accounting and invoicing plan or native payroll options.
The source remains the evidence for history the target does not recreate.
Preserve customer, product/service, invoice and estimate exports plus transactions, account balances, receipts, payments, payroll and tax records relevant to your obligations. Keep the source accessible until every historical and statutory requirement is covered.
Decide which records must operate in Invoice Crowd and which remain in the source archive. Record the cutover date, owners and retention requirements.
Invoice Crowd analyzes CSV, TXT, XLS and XLSX files before supported imports.
Current analyzers cover items, customers, vendors, invoices and estimates. Auto-detection suggests columns, but required fields and warnings must be reviewed before import.
Test duplicate names, foreign currencies, taxes, discounts, long descriptions and open documents. Review the preview and skipped-row output instead of assuming a successful request means every row was accepted.
Activation follows totals, document meaning and ownership, not a raw row count.
Wave accounting transactions, bank connections, reconciliations, receipt images, payroll, tax filings, payment processing, recurring invoices and attachments are not recreated by importing customers, items and sales documents. Establish opening balances and an archive boundary deliberately.
Pause or sequence writes, take final exports, import approved deltas, reconcile opening and open-document totals, and keep a documented fallback path before inviting the wider team.
Migration checklist
Use this checklist with the people responsible for bookkeeping, operations, retention and customer communication.
Keep dated, immutable source exports and access.
Use CSV, TXT, XLS or XLSX within the configured upload limit.
Map required identity and contact fields.
Map supplier identity and contact fields.
Map product and service fields deliberately.
Preserve document number, dates, customer, currency, lines, tax, discounts and totals.
Preserve quote identity, dates, customer and line details.
Review detected headers, suggested mapping, required fields and sample rows.
Resolve missing required fields before committing the job.
Download and review rejected records instead of hiding them.
Match open documents, customer balances and approved opening totals.
Record what remains in Wave and why.
Questions
No. Invoice Crowd currently analyzes and imports supported CSV or Excel data for items, customers, vendors, invoices and estimates. Historical records and provider-specific structures need an explicit archive, rebuild or reconciliation decision.
The current analyzer accepts CSV, TXT, XLS and XLSX files within the configured upload-size boundary.
Items, customers, vendors, invoices and estimates. Bank reconciliation has a separate import workflow and is not a substitute for migrating a complete accounting ledger.
Not immediately. Keep source access and immutable exports until financial, tax, contractual and audit retention needs are covered and every material balance has been reconciled.
Check field mapping, warnings, row outcomes, representative document rendering, open balances, currencies, taxes and approved opening totals. A successful upload or matching row count is not enough.
Document it in the migration register and either preserve it in the source archive, attach it through a supported operational process, or rebuild it deliberately. Never silently discard it.
Create the archive, normalize a representative set, inspect warnings and skipped rows, and reconcile the result before the production cutover.
