---
app: erp
audience:
  - owner
ui_only: false
agent_actions: []
agent_examples:
  - how do I undo a migration I already ran?
  - can the Bakulai team do my migration for me?
  - the migration says no account matches, what do I do?
llm_weight: normal
title: If it goes wrong
description: How to back out of a migration that imported the wrong thing, what
  the Bakulai team receives if you hand it over, and the failures people hit
  most often.
editUrl: true
head: []
template: doc
sidebar:
  order: 7
  hidden: false
  attrs: {}
pagefind: true
draft: false
---

import { Aside } from "@astrojs/starlight/components";

**Who this is for:** an owner who imported something wrong, or who would rather hand the whole thing over.

## Starting over before anything is written

While a migration has created nothing, you can simply drop it. On the first step, the source picker shows **"Locked for this migration."** with a link, **"Start over with a different app"**. That closes the migration and lets you pick a different source and cutoff date.

This works right up until the first document is created. After that the wizard refuses: **"This migration has already created documents. Roll it back instead of cancelling it."**

## Undoing a migration that already wrote

Rollback undoes the **whole migration**, never one step. It walks the list of everything the migration created, newest first, and reverses the import order — prices before products, products before accounts — because a document cannot go while something still points at it.

What happens to each document depends on what it is:

- **Submitted entries are cancelled, not deleted.** A journal that was posted gets a reversing entry, so your ledger goes back where it was. **The cancelled document stays visible**, marked cancelled. That is deliberate: a posted entry that simply vanished would leave a hole in your audit trail.
- **Drafts and master records** — products, prices, customers, suppliers, accounts — are deleted outright.
- **Anything still in use** is left alone and reported. You will see: *"3 documents could not be removed. Open each one, remove what still points at it, then roll back again."* Running the rollback again retries only those.

When nothing is left over, the migration is marked **Rolled Back**, every step returns to Pending, and you can start again from step one with a corrected file. A rollback that leaves something behind keeps the migration open, with the count on screen, so you can clear the blockage and press it again.

You will find it on the **Approve & run** step, under **"Undo this migration"**, once the migration has actually created something. It asks first: *"Remove 12 documents this migration created? Submitted entries are cancelled first. This cannot be undone."*

## Letting the Bakulai team do it

On the first step, under the connector card: **"Would rather not set this up yourself?"** → **"Let the Bakulai team do it for you"**.

You still do three things: pick the app you are leaving, set the cutoff date, and **upload your export files**. The send button stays off until at least one file is there — *"Upload at least one exported file above first."* Then leave a WhatsApp number and, if it helps, a note.

**What we receive:** your company name, the old app, the cutoff date, who asked, your WhatsApp number, the list of file names with their row counts, your note, and a link to the migration inside Bakulai.

**What we do not receive: the files.** They stay inside Bakulai, and the team opens them here. Bookkeeping data does not go into a mailbox, where it would live on in archives and backups that have none of Bakulai's tenant separation.

We reply on WhatsApp, usually within one working day. Available on every plan, including the free one. Pressing send twice does not send a second request — the page simply shows when the first one went.

After you hand over, the wizard steps disappear and the page says **"The Bakulai team has your files"**. Changed your mind or have something to add? Reply on WhatsApp; it is the same thread.

## Common failures

**"No account in Bakulai matches 'Kas Kecil'."** — the account name in your file does not exist in Bakulai's chart of accounts. Either run the `coa` step first so your own chart is there, or correct the name in the file. Only that row fails; the rest still posts.

**"An opening journal already exists for this company (ACC-JV-2026-00007)."** — you get one opening journal and one opening stock per company. Roll the migration back before running the step again.

**"This company has no Temporary Opening account to park the difference in."** — the opening journal needs somewhere to hold a balance-sheet difference. Contact us; it belongs to the company's chart of accounts, not to your file.

**"'SKU-001' has no cost per unit or total value; stock cannot be valued without one."** — opening stock needs the cost per unit, or a total value to divide by the quantity. It has to come from your file: guessing it from a purchase price would quietly value your whole stock wrong.

**"'SKU-002' is tracked by serial or batch number; opening stock for such items is not supported yet."** — those lines have to be entered by hand for now.

**"No Customer in Bakulai matches 'Toko Sinar'. Run the parties step first."** — an aging report gives you a name and nothing else, so opening invoices will not create the contact for you. Run the parties step, then run this one again.

**"Invoice INV-0231 is dated 2026-02-01, after the cutoff date."** — that invoice belongs in Bakulai as a normal invoice, not in the migration. Either remove the row or move your cutoff date.

**"'PT Global' is billed in USD; only IDR invoices can be migrated for now."** — foreign-currency invoices are reported rather than converted at a guessed rate. Enter them by hand.

**"3 figures do not match yet."** — the Verification card compared your files with the books and found a gap. Most often a step has not been run. Fix it, then press **Check again**.

**A banner that locks the run button.** Before an opening step touches your file it checks the company: a fiscal year covering the cutoff, books not frozen over it, no submitted Period Closing Voucher, a Temporary Opening account, a default cost center, the round-off settings. Fix what it names and reload.

**"This step still needs a column for: account_name."** — your AI's mapping left out a required field. Paste the follow-up prompt back into your chat and ask it again.

**"Column Harga does not exist in the file."** — the mapping refers to a column that is not in the sheet. Usually the wrong file got the wrong role, or a header row sits above the real headers.

**"This file has 45,000 rows; a single stage accepts at most 20,000. Split the file."** — exactly what it says.

**"Your plan allows 100 items and you already have 20; this file adds 150."** — upgrade, or split the file and import what matters first.

**"Journal Entry is not included in the Gratis plan."** — this step writes a document your plan does not include. A higher plan fixes it; nothing about your file will.

**The AI never connects.** The chip stays on *"Waiting for your AI to connect…"* until your AI actually calls the connector. Ask it a question — copying the address alone does nothing. See [Connect your AI](/erp/migration/connect-ai/).

**A step finished but numbers are wrong.** A step reports **Completed** even when some rows failed, so read the three counts, not the status. The failed rows are listed underneath with a reason each.

## Still stuck

Email **support@bakulai.com** with your company name and the migration's link from the address bar, or use the assisted path above — it puts the same information in front of us in one press.

## Related

[Move in from another app](/erp/migration/overview/) · [What moves, step by step](/erp/migration/stages/) · [Opening balances](/erp/migration/opening-balances/)