Migration
QBD users have been burned by migration promises before. Here's what we can verify, what we'll message carefully, and what won't make the first beta wave.
Your original QuickBooks® Desktop data stays with you
Your original QuickBooks Desktop company file (.QBW) stays where it is. Our goal is to export the accounting data needed for migration without modifying the original company file, so your existing Desktop workflow and backup process stay intact throughout the cutover.
If JouraBooks doesn't work for your business, your original QBD setup is exactly as you left it.
Target beta migration scope
These are the areas we think matter most for a credible QuickBooks Desktop migration: the bookkeeping structure, the open work that still needs action, and the history required to reconcile core reports after cutover.
- ✓ Chart of accounts and opening balances
- ✓ Customers + jobs hierarchy
- ✓ Vendors (including 1099 eligibility)
- ✓ Items, terms, tax codes, and tax items
- ✓ Open invoices, bills, and purchase orders
- ✓ Historical transactions needed to reconcile core reports
Advanced areas we will message carefully
- Class-based segment reporting
- Important for businesses that report by department, location, property, or profit center. We will only market this as beta-ready once the class list, historical assignments, and reporting outcome are preserved.
- Inventory costing and quantity valuation
- Inventory needs a careful closing-date decision, cost layering review, and reconciliation plan. We expect to handle it deliberately rather than hand-wave it as a simple import.
- Payroll history
- Payroll often needs a different migration path than core bookkeeping data. We would rather define the exact beta handling up front than imply full payroll parity too early.
- Custom reports and custom fields
- These matter, but they are not the first thing buyers use to verify a successful migration. Core balances, open A/R and A/P, taxes, and report reconciliation come first.
Likely not in the first beta wave
- – Multi-currency conversions (USD only at beta)
- – Online bill pay integrations
- – Attachments and payment-processor history that depend on third-party services
- – Exact QuickBooks Desktop custom report layouts
We'd rather publish a sharp scope boundary than imply parity we have not earned yet. If one of these matters to your business, tell us on the beta form so it factors into prioritization.
How we expect to validate the migration
We think migration trust comes from reconciliation, not from a long feature checklist. The target is to validate the reports accounting teams check first before they cut over.
- ✓ Trial balance and key balance-sheet totals
- ✓ Open A/R and A/P aging after migration
- ✓ Tax setup and the transaction history needed for core report comparison
- ✓ A clear callout for anything that still needs manual cleanup before go-live
If a data area cannot be verified cleanly, we should describe it as planned or limited, not market it as done.
Accountant-led migration
If you manage books for multiple clients on QuickBooks Desktop, we're building batch migration tooling with you in mind. Tell us on the beta form how many clients you run and we'll make sure your priority reflects that. Select early partners may receive one-on-one migration support.