Migrate to Ondes PRO from another tool, with the API and AI

What can be imported into Ondes PRO, and in what order?

Import your data into Ondes PRO, step by step

Running example: Atelier Lumen is bringing over 412 products, 1,380 customers and 37 invoices awaiting payment.

1. 1

   Export from the old tool

   Get one CSV file per object type: products, customers, open invoices with their lines. Keep the original identifiers in a column: they become your idempotency keys and your mapping table.

2. 2

   Connect your assistant to your workspace

   Connect Claude Code, Cursor or another MCP client to your workspace’s server through OAuth (see compatible clients). For an unattended script, create a dedicated key with shop:write and billing:write instead, and revoke it once the migration is done.

   bashCopy

   claude mcp add --transport http ondes https://your-workspace.ondes.pro/mcp/

3. 3

   Have the column mapping drafted

   Hand the export to the assistant. It reads each resource sheet with ondes_ressource — required fields, types, accepted values — and drafts a mapping: “Label” to name, “Net price” to price, “Ref.” to sku. Review it: this is the one moment a human really has to decide.

4. 4

   Dry-run a sample

   Ask the assistant to validate a dozen rows with simuler: true: the server checks each body and answers as it would for a real creation, without saving anything. Bad formats (prices with a currency symbol, VAT written “20 %”, country names spelled out) surface here, field by field.

5. 5

   Import in batches of 100

   POST /api/v1/<resource>/lot/ writes up to 100 objects in one transaction: if a single row is rejected, the whole batch rolls back and the response points to the row and the reason. Add an Idempotency-Key derived from the batch’s original identifiers, so re-running after a dropped connection creates no duplicates.

6. 6

   Bring billing over last

   Create quotes and their lines first (a quote’s numero is optional: left empty, it takes the company’s sequence), then one invoice per quote. Dry-run each invoice before the real write: once created, it can no longer be deleted.

7. 7

   Check the result

   Compare totals: number of products, number of customers, amount of open invoices. The ?search= filter on shop/produits (name or SKU) and billing/clients (name or email) quickly finds a missing row. The assistant can produce this reconciliation report itself.

The assistant reads the export and dry-runs before writing

A customer batch body

Each operation carries its method and its data; an id is only required to update or delete an existing object.

curl -X POST https://your-workspace.ondes.pro/api/v1/billing/clients/lot/ \
  -H "Authorization: ApiKey opk_…" \
  -H "Idempotency-Key: customer-import-batch-001" \
  -H "Content-Type: application/json" \
  -d '{
    "operations": [
      {"methode": "POST", "donnees": {"nom": "Brasserie La Canopée", "email": "accounts@lacanopee.com", "ville": "Nantes"}},
      {"methode": "POST", "donnees": {"nom": "Galerie Ressac", "societe": "Ressac SAS", "siret": "…", "ville": "Biarritz"}}
    ]
  }'

A hundred operations per batch at most. One rejection, and nothing is written.

Classic data-migration traps

• Duplicate customers: the same customer entered twice in the old tool. De-duplicate on email or company registration number before importing; the assistant can do it on the CSV.
• Gross amounts mistaken for net: Ondes PRO prices and lines are entered excluding VAT, with a VAT rate per line. Check on two or three invoices that the recomputed totals match.
• Images: they are uploaded separately, as multipart, to shop/images-produit once products exist. A batch does not carry files.
• Companies: if your workspace holds subsidiaries, each object belongs to the company of the call. Import company by company, without mixing files.
• The forgotten key: revoke the migration key at the end. An OAuth connection is cut by name from the MCP tab.

What if I don’t have a developer?

Going further

• Online storeOrders, catalogue, promo codes and shipments handled by your assistant, in test mode by default.Read
• InvoicingQuotes, invoices, reminders and credit notes prepared by your assistant, within invoicing rules.Read
• Inventory managementStock levels, deliveries, bills of materials and production orders read and prepared by your assistant.Read
• CRMCustomer records, follow-up notes, pipeline and reminders kept up to date by your assistant.Read

Frequently asked questions

Read next

• Connect your websiteShow the catalogue and take Stripe payments from a site that is already live, without rebuilding it.Read
• Build an integrationScoped keys, signed webhooks, idempotency and test mode for a back office that never creates duplicates.Read
• Automate with AIReminders, reports and automations described in one sentence, always reviewed before anything runs.Read