---
app: erp
audience:
  - owner
ui_only: false
agent_actions: []
agent_examples:
  - how do I add the Bakulai connector to Claude?
  - do I need a paid ChatGPT plan to migrate?
  - can the AI change my data during a migration?
  - can the Bakulai AI Assistant do my migration?
  - the migration wizard says the AI Assistant is not set up
llm_weight: normal
title: Connect your AI
description: Let the Bakulai AI Assistant read your export files and propose the
  mapping, or add the migration connector to Claude, ChatGPT or any app that
  speaks MCP so your own AI does it.
editUrl: true
head: []
template: doc
sidebar:
  order: 4
  hidden: false
  attrs: {}
pagefind: true
draft: false
---

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

**Who this is for:** an owner doing the migration themselves. If you chose **"Let the Bakulai team do it for you"**, you can skip this page entirely — the team needs no AI account from you.

## Two ways to bring an AI

Reading an export file means guessing what a column called *Kode Brg* or *Hrg Jual* is supposed to be. That guess is what an AI is good at, and it is the only part of a migration that needs one. Bakulai itself does not guess; an AI does, and you pick which one in the wizard's first step:

- **Bakulai AI Assistant** — the AI panel beside the Desk, listed first. It has to be set up once with an AI you connect ([The AI assistant in the Desk](/erp/ai/ai-assistant-in-desk/)).
- **Your own AI** — Claude, ChatGPT or another app, through a connector limited to this one migration.

Both are free on every Bakulai plan, including the free one: you pay your AI provider for the tokens, not us.

## Bakulai AI Assistant

<Steps>

1. In the wizard's first step, keep the **Bakulai AI Assistant** tab.

2. If it says the assistant is not set up yet, press **Set up the AI Assistant first**. The panel opens on its setup; connect an AI there — it takes about a minute — and come back. The wizard notices by itself. Only a Tenant Admin can set the assistant up.

3. In step two, upload your files and press **Ask the AI Assistant**. The panel opens a **new conversation** with a message about this migration already in the box. Read it, then press **Send** — nothing is sent for you.

4. The assistant reads each step's columns and proposes a mapping, one step at a time, and tells you which columns it skipped and why.

</Steps>

<Aside type="note">
  **Start it from the wizard.** A conversation becomes a migration conversation only when its first message is sent from the wizard page, so an older conversation in the panel cannot propose mappings. If some rows fail on **Approve & run**, press **Ask the AI Assistant to fix it** there.
</Aside>

In a migration conversation the assistant gets two extra tools: one reads the migration — the same information as the six reading tools below — and one saves its proposed mapping. **It has no tool to run an import.** Proposals need no approval card, because they write nothing into your books; the import still waits for your button. This works on the free plan too, where the assistant otherwise only reads.

## Your own AI, through the connector

## What the AI can and cannot do

The connector gives your AI **seven tools. Six only read**: which migration is open, what to export from your source app, which steps exist, what fields a step accepts, the rows that failed, and a summary. **The seventh saves the mapping your AI proposes** — as a proposal you review and approve in the wizard; nothing is imported until you press the button.

There is **no tool to run an import and no tool to upload a file.** That is the actual safeguard — not the sentence in the prompt asking the AI to behave. Even an AI that decided to ignore every instruction could not write a single row into your books. Approving and running is a button in Bakulai, pressed by you.

To propose a mapping the AI sees your **column headers and a few sample rows**, not the whole file.

## Which app to use

| | What it costs |
| --- | --- |
| **Claude** | A free Claude account is enough. |
| **ChatGPT** | Needs a paid plan: Plus, Pro, Business, Enterprise or Edu. |
| **Another app** | Anything that can add a remote MCP server — Claude Desktop, Claude Code, Cursor, VS Code Copilot. |

The address you will paste is shown in the wizard with a **Copy** button next to it:

```
https://erp.bakulai.com/mcp/migration
```

## Claude

<Steps>

1. Open **Customize**, then **Connectors** — it sits under Settings on some builds.

2. Press the plus button, then **Add custom connector**.

3. Paste the address above and press **Add**.

4. Sign in with your Bakulai account when Claude asks.

</Steps>

<Aside type="note">
  On a Team or Enterprise account an Owner adds it once first, under Organization settings → Connectors → Add → Custom → Web. Everyone else then presses **Connect** on it under Customize → Connectors.
</Aside>

## ChatGPT

<Steps>

1. Open **Settings**, then **Plugins** — older accounts call the same page *Apps*, or *Connectors*.

2. Turn on **Developer mode**. It sits at the bottom of that page, or under Advanced on older accounts.

3. Press the plus button, or **Create**, to make a new connector.

4. Give it a name, paste the address above as the MCP server URL, and confirm that you trust the provider.

5. Sign in with your Bakulai account when ChatGPT asks.

</Steps>

<Aside type="caution">
  **Type the prompt in a chat.** In voice, only ChatGPT's **Live** option can use the plugin, and a migration is easier to follow on screen. In a managed workspace an admin has to allow custom connectors first, and you may have to switch the connector on inside each new chat.
</Aside>

## Another app

<Steps>

1. Find where the app adds an MCP server. It is usually called connectors, plugins, tools or MCP servers.

2. Add a **remote**, or HTTP, server and paste the address above.

3. Leave the authentication as **OAuth**, then sign in with your Bakulai account when the app opens the browser.

</Steps>

The app has to support remote MCP servers with OAuth. One that only runs a local command cannot reach Bakulai.

## Knowing it worked

With the AI Assistant, the first step shows **"Your AI Assistant is set up"** as soon as the panel has an AI, and step two shows **"The AI Assistant has read the files"** once it has read a step's columns.

With your own AI, the wizard shows **"Waiting for your AI to connect…"** until your AI actually calls one of the seven tools. Copying the address is not enough — the chip only turns to **Connected** once a real call arrives, and it names the app that made it.

If it stays waiting: ask your AI something simple like *"what migration is open in Bakulai?"*. Signing in is part of the first call, so nothing happens until you send a message.

## Then what

With your own AI: go to step two, upload your files, and press **Copy the prompt**. Paste that into the same chat where you added the connector. The prompt tells your AI to read each step's fields and propose a mapping, and ends with:

> Do not run or start the import. I will approve each stage in Bakulai myself.

Your AI reports back which columns it skipped and why. You read that on the **Summary** step and approve on **Approve & run**.

## Related

[Export your files](/erp/migration/prepare-files/) · [The AI assistant in the Desk](/erp/ai/ai-assistant-in-desk/) · [What moves, step by step](/erp/migration/stages/) · [If it goes wrong](/erp/migration/rollback-and-support/)