Moving to BaseCloud from another accounting system¶
Moving your books is what accountants call a conversion. You pick a start date. Everything before it comes over as balances: your old trial balance on the day before becomes your opening balances, and what customers still owed then comes over as open invoices and credit notes they can still pay. From the start date on, BaseCloud is your books.
- Your CRM keeps the history. Clients' open invoices, the payments made on them since, and their unused credit come over. Paid invoices from earlier can come over too, so statements and what each client has spent are complete.
- Your books start cleanly. Only what happens from the start date counts in your profit and loss and your sales tax reports.
- You prove it. Check your move compares your old books with BaseCloud's, account by account and customer by customer, and shows what differs.
Pick how you'll move¶
| Coming from | How |
|---|---|
| Xero | The built-in move. See Move from Xero. |
| QuickBooks Online | The built-in move. See Move from QuickBooks. |
| Sage Accounting (South Africa) | The built-in move. See Move from Sage. |
| Anything else (QuickBooks Desktop, Pastel, Wave, FreshBooks, a spreadsheet) | Export from your old system and bring it in with a workflow, the batch import or the AI connection. See From any other system. |
The built-in move, in short¶
The move reads your old books through your own connection to Xero, QuickBooks or Sage. It only reads: nothing is changed in the old system, no automations start, and nothing is sent to your clients.
- Pick your start date: the first day of a financial year, or at least of a tax period, so no tax return is split between two systems. See Start date.
- Connect your old system in Settings › App Connections & Keys, or with + New Connection in the Move from list when you preview the move. A connection that needs signing in again shows Reconnect there too.
- Start your books with that start date and the chart imported from the same connection. BaseCloud support does this with you. See Start your books.
- Preview the move in Settings › Books › Move from Xero, QuickBooks or Sage: pick the connection, the organisation and the start date, and click Preview. It shows what will come over and what the old system says customers owed. Nothing comes over yet.
- Bring it over. Click Bring it over and keep the page open while it works, or close it and click Carry on later.
- Bring paid history over if you want it (Xero and QuickBooks).
- Check your move, and fix anything that differs.
- Set a lock date.
You need Manage Accounts (a books right) and Manage Users. The move can be previewed, and clients and invoices brought over, before your books are on; the opening balances wait until they are.
What comes over¶
| Step | What comes over |
|---|---|
| Clients | Your customers (not suppliers). Each is matched to a client already in BaseCloud: one from an earlier move, then the one client with the same email address, then the one client with the same name. Never a guess between two: a new client is made, and the preview lists them under Clients to check after the move so you can merge them afterwards. |
| Pricebook items | Your items, where their code isn't in your Pricebook yet. |
| Open invoices and credit notes | Every invoice and credit note still open on the day before your start date, each on its own date with its own lines, its old number as its Reference, its total checked to the cent and its tax as the old system rounded it. What was paid on an invoice by that day is one payment, so the invoice opens owing what it owed. |
| Payments since the balances day | Payments made on those invoices from your start date on, each on its own date with its reference. These are real money in your new books. |
| Unused payments, kept as credit | Overpayments and prepayments not used by the day before your start date, as each client's credit. |
| Trial balance as opening balances | Your old trial balance on the day before your start date becomes your opening balances (Xero and QuickBooks), every account but Accounts Receivable, which comes from the open invoices. |
What doesn't come over, and why, is listed in the preview:
- Invoices and credit notes dated on or after your start date. Make them in BaseCloud, or choose a later start date.
- Credit used on an invoice after the day before your start date in the old system: use it again in BaseCloud.
- Anything in another currency, and open items with no customer or no date.
- Bills and suppliers: BaseCloud doesn't have bills yet. Put what you owed suppliers in your opening balances (it comes with the trial balance).
- Repeating invoices, quotes, bank transactions and reconciliations. Set up recurring invoices and bank accounts in BaseCloud.
If something can't come over¶
A record the move can't bring over (a total that doesn't match, a client that can't be made) is listed with the reason and skipped; everything else carries on. Fix what each says, here or in the old system, then click Try these again.
When the opening balances wait, the move says why: the books aren't on yet, they start on another day than the move (preview it again with the books' start date), or some accounts in the old trial balance aren't in your chart (add them in Accounting › Chart of accounts with the same code, then Carry on).
Paid history¶
Optional, after the move (Xero and QuickBooks). Under Paid invoices from before your start date, pick the From date and click Bring the history over. It brings over invoices from that date up to the day before your start date that were paid in full by then, each with the payments that paid it, so your clients' history and statements are complete. There's no end date to pick: history always runs up to the day before your start date, where the move's own invoices take over. It changes no balance in your books. Run it again with the same From date to retry any that failed: what's already here is skipped.
Check your move¶
Under Check your move, click Check your move. It compares the old system with BaseCloud on the day before your start date:
- Every account in the trial balance, the old system's figure beside BaseCloud's, and the difference.
- What each customer owed, side by side.
- How many documents came over each year.
- Historical Adjustment: zero once everything is in.
It says Proven when nothing differs. Show only what differs hides the rest. The same check is a report card on the Reports page (Check your move, in the Books group), to keep or print.
If a customer is out, look for an invoice, credit note or payment that didn't come over, or came over with the wrong date or amount. Fix it and check again. A statement for that customer shows everything they had.
How old documents land in your books¶
An invoice, credit note or payment dated before your start date doesn't post to sales or tax. That year was closed, and its tax filed, in your old system. Instead it changes what that customer owed on the day before your books start: their opening Receivables (what customers owe you).
Each time one is added, changed, voided or paid, BaseCloud moves that customer's opening receivable with an Opening balance change journal, dated the day before your start date:
| Account | Debit | Credit |
|---|---|---|
| Accounts Receivable, for that customer | the change | |
| Historical Adjustment | the change |
That's for an old invoice, which adds to what the customer owed. An old payment or credit note does the opposite: it lowers what they owed, so the sides swap. (The built-in move and the batch import bring a whole batch in line at once.)
Historical Adjustment is the account that holds whatever your opening balances don't yet explain. While you're still bringing things over, it isn't zero. When everything from your old system is in, it is zero: that's how you know the move is complete. See Opening balances.
You can bring documents over before or after your books are switched on. The result is the same.
On the cash basis, money collected after your start date on an invoice that was open then counts as income and tax when it comes in, as it would have in your old system. See Cash or accrual.
From any other system¶
Export your clients, open invoices and credit notes, and payments from your old system, then bring them in.
1. Pick your start date and start your books¶
As above. Then type or paste your old trial balance on the day before the start date into Opening balances: every account but Accounts Receivable.
2. Bring your clients over¶
Use the import template, or the New Client task in an automation. The task's Registered Date keeps the day each one became a client.
3. Bring your documents and payments over¶
Pick whichever suits the size of the job:
- A workflow with the BaseCloud Accounting task, looping over your export: Create Invoice (and Create Credit Note) with Date, Reference (the old number), Expected total and Tax amount, then Mark Quote / Invoice Paid for each payment, finding the invoice by Or find it by its Reference with the Client ID, with its Date paid, Amount and payment Reference. Set Old document: don't start automations to Yes, never start them.
- The batch import through the API: up to 200 old invoices, credit notes and payments a call, each with its id in your old system, in order (a payment can name an invoice made earlier in the same call). Each comes back created, existing or failed. Make the API key with What it can reach set for moving history in, for a higher limit.
- The AI connection: ask Claude to import a batch of old documents (up to 100 at a time) from what you paste or attach. It needs an admin.
Unused credit in your old system comes over as a credit note on its own for the client (no invoice), or as a payment with no invoice.
A payment's method can be named as your old system names it: Check, ACH, Cash, or one of your own payment methods by its name, such as Venmo. Add your own methods before you import, or those payments are refused (leave the method out for Other).
To keep your old invoice numbers, set Next number in Settings first; an imported document keeps its own number when no document in BaseCloud has it.
Running it again¶
Something went wrong halfway? Run the whole import again:
- With If the client already has this Reference on Use that document, a document whose Reference the client
already has isn't made a second time: the task carries on with the one that's there (
was_createdisfalse). If its total or date differs from the one in your export, the run stops and says so. - A payment with a Reference is never recorded twice: the same Reference, amount and date is found and
was_recordedisfalse. - So let every step run on a re-run. Don't skip Mark Quote / Invoice Paid when
was_createdisfalse, or a payment that failed the first time is never recorded. - The batch import and the built-in move are re-runnable the same way: each old record is brought over once.
Choose Create a new one only when a Reference isn't unique to one document, such as a customer's PO number that can appear on several invoices.
4. Prove it¶
Put these report cards on a dashboard, dated the day before your start date, and compare each with the same report from your old system:
- Aged receivables: what each customer owed. It should match customer by customer.
- Trial balance: every account. It should match line by line.
- Historical Adjustment is zero on the trial balance.
Set a lock date¶
Last step, whichever way you moved, once the move is proven: set a lock date. It can be any day from your start date on; usually it's the end of the first month you close in BaseCloud. From your start date on, BaseCloud is your only system of record.
Once a lock date is set, no invoice, credit note or payment dated before your start date can be added, changed or voided, because it would change opening balances you've proved. BaseCloud refuses it and tells you why. To change one later, clear the lock date first. Old invoices that were still owed can be paid as usual: a payment dated after the lock date posts like any other.