Repository navigation
A simple "move your books in" migration path, reusing the existing Import module #1376
naoswilbrink
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Spun out of #1371. The webapp being desktop-only is one friction point; getting books into Bigcapital in the first place is another, and this one is mostly a packaging problem — the import machinery already exists.
Context: I recently migrated a real company's first-year books (cash basis, coming off QuickBooks + spreadsheets) into a self-hosted instance. It worked, but only by writing an API client — there's no guided path, even though ~90% of what one needs is already in the
Importmodule.What already exists (and works)
packages/server/src/modules/Import+ the webapp<ImportView>wizard (dropzone → column-map → preview → commit), with a downloadabletemplate and per-row error reporting for every resource.
items, item categories, tax rates, manual journals, expenses, invoices, estimates,
receipts, credit notes, bills, bill payments, payments received, vendor credits,
uncategorized bank transactions.
Journal Nointo one balanced multi-line journal (transformInputToGroupedFields).opening-balance-equityandopening-balance-liabilitiesexistout of the box.
/accounts/import,/manual-journals/import,/items/import,/customers/import,/vendors/import,/invoices/import,/estimates/import,/receipts/import,/expenses/import, …Implication: opening balances and historical GL are already importable today via the
manual-journals CSV (one row per account, all sharing one
Journal No, publish = T).Nobody knows this because nothing frames it as "migration."
The gap
know the dependency order (accounts → contacts → items → opening balances → open
AR/AP → historical GL).
manual-journal import with a sample sheet full of
lorem ipsum.export, but you reshape every file by hand to Bigcapital's column names.
no reconciliation history.
below).
Proposed path — smallest thing that helps, in order
Phase 1 — a Migration hub page (webapp only, no backend)
A
/setup/migration(or Preferences → "Import & migration") page that is just anordered checklist linking the existing import wizards, with progress persisted to a
SETTINGSrow:/accounts/import/manual-journals/import(pre-selected "opening balance" preset — see Phase 2)/customers/import/vendors/import/items/import/invoices/import/bills/import/manual-journals/importEach step: one-line "what this is / what you need", link, and a "done" check. No new
import logic. This is the 80/20.
Phase 2 — an "Opening balances" importable
A thin
OpeningBalancesImportable extends Importable(mirrorsManualJournalImportable) whose columns areAccount, Debit, Credit, As-of dateandwhich builds one balanced journal, auto-plugging any rounding to
opening-balance-equity. It's a friendlier front-end to what manual-journals importalready does. ~one importable class + sample data + a route. Reuses the whole wizard.
Phase 3 — incumbent mapping presets
The column-mapping step already supports saved mappings. Ship named presets for the
common exports:
Plus a short docs page per source ("export these 5 reports from QuickBooks, upload in
this order"). Mostly docs + a JSON preset file per source; no engine changes.
Phase 4 (later) — coverage holes
FixedAssetsImportable(cost, accumulated depreciation, in-service date, method).before the books-start date) and raises the throttle ceiling for the session.
Non-goals
Effort
Phases 1–2 are a weekend. They'd have turned the case-study migration from "write a
Python client" into "upload 6 CSVs in order."
All reactions