Skip to content

What moves, step by step

Who this is for: an owner on the Summary or Approve & run step, deciding what to press.

A migration is not one big import. It is a list of steps, each fed by one of the files you uploaded, each approved and run separately. If one step goes badly, the others are untouched.

The wizard labels the steps with their internal keys — coa, items, item_prices, parties. Those are the names you will see on screen, so they are the names used here.

Step What it creates Works today
items Products, with unit, category and barcode Yes
item_prices Selling prices Yes
parties Customers and suppliers Yes
coa Your chart of accounts Yes
opening_gl The opening journal entry Yes
opening_stock Opening stock per warehouse Yes
opening_ar_ap Unpaid customer and supplier invoices Yes
sales_history — Always skipped

Every step now works. opening_ar_ap is the only one that needs a particular plan — it writes Sales Invoices and Purchase Invoices, so it needs one that includes Inventory & AR/AP.

When the last step finishes, Bakulai checks its own work — see Opening balances. You do not approve that; it runs by itself.

If you upload a sales-history file, it gets a step of its own that is always skipped, with the reason on screen: “Sales history is not migrated — only balances move. Your old transactions stay readable in the old app.” It is shown rather than ignored so you can see the file was read and deliberately not used.

The first four steps run one row per document. The opening steps are different: they read the whole file at once and build a single document from it, because a balance sheet only balances if every line is there.

A step will not run until the steps it depends on have finished. The wizard says so plainly: “Run ‘items’ first — item_prices depends on it.”

That is not bureaucracy. A price has to belong to a product, and a product has to belong to a chart of accounts that already exists. Opening invoices need their customers and suppliers, so parties has to have run — a line whose party is missing is reported rather than guessed into existence. The safe order is the order in the table above, top to bottom.

Steps you have no file for are simply skipped, and a skipped step never blocks a later one.

The opening steps check the company itself before they touch your file, and the wizard shows what failed as a banner that keeps the run button locked. It looks for a fiscal year covering your cutoff date, books that are not frozen over it, no submitted Period Closing Voucher, a Temporary Opening account, a default cost center, the round-off settings, and — the one people hit — an opening journal or opening stock that already exists for this company.

Fixing the cause and reloading clears the banner. Nothing is written while one is showing.

“Not in your plan”, in orange, is the one you are likely to meet. The step exists, but your plan does not include the document it writes, and the message names it: “Journal Entry is not included in the Gratis plan.” Upgrading unlocks it.

All three opening steps need a plan that includes Inventory & AR/AP. The opening journal writes a Journal Entry, opening stock writes a Stock Reconciliation, opening invoices write Sales and Purchase Invoices — every one of those sits in that feature set. A step is locked whole, not half: opening invoices are gated even though only the purchase side is in the set, because half an aging report is worse than none.

Products, prices, contacts and the chart of accounts are available on every plan, including the free one.

A greyed-out step that instead says a thing is not migrated at all — sales history — is not about your plan, and no upgrade changes it.

Migration is not a back door around your plan’s product quota. Before the items step runs, Bakulai counts:

Your plan allows 100 items and you already have 20; this file adds 150. Upgrade your plan or split the file.

The count happens once, at the start of the step, so you find out before anything is written rather than halfway through.

Separately, any single step accepts at most 20,000 rows. Bigger than that, split the file.

On the Summary step each row carries a pill:

  • Waiting for your AI — no mapping proposed yet. Paste the prompt into your AI.
  • Mapped — your AI proposed a mapping, waiting for you.
  • Not in your plan — as above.

On Approve & run, only steps that are actually waiting for you show an Approve & run button. Everything else shows its status as plain text. Approving and running are one action — there is no separate save.

The step keeps going in the background, in chunks, and the screen updates itself. You can close the page; the work does not stop. Each step reports three numbers:

  • created — rows that became documents.
  • skipped — rows that were empty, or that a previous run already created. Re-running a step never duplicates what it already made.
  • routed — rows that belong to a different step. A receivables line on your balance sheet is not an error; it is posted by the opening invoices step instead, and it says so: “‘Debtors’ is created by the opening invoices step, not by the opening journal.”
  • failed — rows Bakulai could not use.

A step with failed rows still finishes as Completed. That is deliberate: the rows that worked are worth keeping, and you should not have to re-run a 3,000-row file because eleven lines were wrong.

The damage is in the numbers and in the list underneath — “Some rows did not import:” followed by Row 47 — message. Press Copy the follow-up prompt and paste it back into your AI; it is built from those failures and asks for a corrected mapping.

Fix the file or the mapping, then run the step again. Rows already created are skipped, so only the ones that failed are retried.

Connect your AI · Opening balances · If it goes wrong