Skip to content
Moving your books in

Set your Migration Boundary

Updated Sep 22, 2026Web

The day your old system stopped and Pippin's books start. Every opening import is dated from it, and it locks on the first import.

Before you start

The Migration Boundary is one date: the last day your old system is authoritative, and the day Pippin’s books open.

It is not a preference. Every part of the opening import measures from it — the opening trial balance is dated at it, Balance-Forward Invoices are dated at it, and the age of everything your Clients owe is counted from it rather than from today.

A month on or after the Boundary cannot be imported as a prior monthly total, because it is already in the ledger and a summary beside it would be counted twice in the same P&L. Pippin refuses those rows and names the boundary in the refusal.

Pick the end of a month, and ideally the end of a quarter or a fiscal year — it is where your old system’s figures are already agreed.

What comes across

A Migration brings the position your books are in and the documents still outstanding. It does not bring your history.

Arrives Does not
The opening trial balance, as one balanced entry Closed Invoices
Open Bills, at their original dates Historical Payments
What Clients still owe, as Balance-Forward Invoices General ledger detail
Chart of Accounts, Clients and Services
Prior monthly totals, for reporting only

The third refusal is a choice rather than a wall, and it is the one worth understanding. An opening trial balance already carries every prior year’s result inside retained earnings. Importing the detail behind those years would count the same profit twice — once as history, once as equity.

Vendors arrive with the Bills you owed them — importing open payables creates every vendor behind them, so there is no vendor step to run first. Vendors you were square with are a separate, optional import on the Vendors page.

Prior monthly totals are the exception to all of this. They never reach the ledger. They are income and expense figures from before the Boundary, kept so a year-over-year report does not fall off a cliff at the cutover.

Steps

Settings, Import your books, with the Migration boundary date field above the numbered import steps
The boundary is answered once, above the steps — so every import below is measured from the same date.

Good to know

The Boundary locks on the first import. It has to: everything already taken is dated against it. It releases on its own once nothing imported remains, so the way to change your mind is to undo the imports — Settings › Import your books, one batch at a time.

Found three Bills and two Invoices you missed? Run the Import again. A re-run adds: it takes what is new and refuses every document it has already taken. There is no need to start over, and no way to double up by trying.

Rehearse first. An open receivables import creates real, finalized Stripe invoices against real customers, and the only way back from a mistaken batch is voiding them one at a time. Settings › Import your books offers a sandbox Org at the top of the page for exactly this — and because a sandbox runs on Stripe test mode, there is no promote: you rehearse, learn what your exports need, throw it away, and then do it once for real.

This article is maintained alongside the import flow. If a step here does not match what Settings › Import your books says, the app is right and this is stale — tell us and we will fix it. Last reconciled against the flow on 22 September 2026.

Didn't solve it?
Beta support answers within one business day.