The biggest reason owners stay with an old POS app is not satisfaction, it is fear of losing data: thousands of products, customer lists and stock counts that took weeks to build. The good news is that switching POS apps does not have to mean retyping everything. This article explains the Bakasir Migration Engine: what it moves, what it does not, and how to undo it if the result does not match.
What data can be moved
The migration engine works with the "datasets" you upload. These are recognized:
| Data | What comes across |
|---|---|
| Products | Name, code or SKU, barcode, category, brand, unit, selling price, cost, wholesale price, tax, low-stock threshold, variants |
| Customers | Contact details, tax number, address, group, opening balance (receivable) and points |
| Suppliers | Contact details, tax number, address and opening balance (payable) |
| Stock | Quantity and cost per outlet, including batch number and expiry date where present |
| Outlets and business profile | Name, address, contact and tax number |
| Staff | Name, email, role and outlet |
| Sales and purchase history | For sources that provide it, such as a Stocky export |
Products are required. Customers, suppliers and stock are strongly recommended. Transaction history is imported as a fixed record and does not move stock again, because stock comes from the per-outlet stock data.
Which old POS apps are recognized
Bakasir has dedicated profiles that recognize export patterns from Moka, majoo, Qasir, Olsera, Pawoon, Kasir Pintar, Stocky and OpenSourcePOS database dumps. For any other app, upload a CSV, Excel or SQL file and map the columns yourself.
Accepted file formats are CSV, Excel (.xlsx and .xls), ZIP, SQL dumps, and SQLite or database files (.sqlite and .db). You can upload several files at once, each up to 2 GB. Large files are sent in chunks and can resume if the connection drops.
How to switch POS apps, step by step
Only the Owner can start a migration. Go to Catalog → Import Products and click Move from another POS. The migration screen has six steps:
- Upload. Choose the "Previous POS" if you know it. This shows a guide for exporting the right files and helps when auto-detection is unsure. Then drop in your files.
- Scan. Bakasir identifies the source POS, lists the files it found with their row counts, and tells you about any required file that is missing.
- Mapping. Each column from the old app is matched to a Bakasir field. Green means a confident match; review the yellow and red ones. Outlet names from the old app are also matched to your Bakasir outlets.
- Issues. Bakasir checks the data for things like invalid amounts, duplicate codes or negative stock. Issues marked "Blocking" must be fixed; "Warning" rows still import but deserve a look. You can download the issue list as CSV.
- Preview. Press Rehearse the import for a dry run. You see how many rows will be created, linked to existing data, skipped or rejected.
- Apply. Once the numbers look right, apply to your store.
Nothing is written to your store until you press Apply, so steps 1 to 5 are safe to repeat as often as you need.
Merge or replace: two migration modes
At the preview step you choose a mode:
- Merge with existing data. Existing Bakasir data is kept; matching records are linked and new ones are added. This is the safe choice if your Bakasir store already holds something.
- Replace all data. All business data in the store is deleted and refilled exactly as in the migration files. Bakasir first creates an automatic backup named "pre-migration-replace". This mode is meant for a freshly created store or test data, and its button must be held down to confirm.
Check the result with the reconciliation report
After applying, Bakasir shows a reconciliation report comparing the old app's figures with Bakasir's: row counts per file, stock quantity and value per outlet, stock ledger integrity, customers with receivables and points, suppliers with payables, and cross-references. Each check is marked OK, Review or Failed. If something says Review or Failed, look at the difference before moving on.
Finalize or roll back
Until you finalize, a migration can still be rolled back: everything it added is removed again. Rollback is blocked once imported data has been used by sales, purchases or stock movements, so decide soon after checking the report. Finalizing is permanent and asks you to acknowledge the list of data that was not migrated. Temporary uploaded files are deleted automatically after a migration is finalized.
What does not come across
Not every concept in the old app has an equivalent. Bakasir shows a "data not migrated" list before you apply, for example modifiers and menu add-ons, recipes, serial numbers, service charges, or rows in other tables such as logs and old app settings. You must acknowledge that list before finalizing. Settings such as tax, receipts and payment methods need to be set up again in Bakasir; the business setup guide covers them.
Checklist before you press Apply
- Take a backup in the old app, and do not delete the old account yet.
- Make sure stock in the old app was counted recently.
- Check your plan limits. Product count limits apply on each plan, especially Free.
- Migrate during a quiet period, not at peak hours.
- When done, sell one test item and verify its stock.
Next steps
Once your data is in, set up tax, receipts and stock by following the guide to controlling your stock. If you are still comparing apps, see the POS selection checklist and the plan details on the pricing page.
Ready to try it yourself? The Free plan has no time limit and needs no credit card.
Keep reading
How to Choose a POS App for Your Small Business: A Practical Checklist
Stock Management for Grocery Stores and Minimarkets: Low Stock, Counts, and Transfers
Free POS App: What You Really Get, and Where the Limits Are
Frequently asked questions
Does my old sales history come across?
It depends on the source. The migration engine can import sales and purchase history from sources that provide it, such as a Stocky export. For other sources, products, customers, suppliers and stock are the core of what moves. Keep your old reports from the previous app as an archive.
What if the migration result turns out wrong?
As long as it is not finalized and the data has not been used by transactions, you can roll the migration back and everything it added is removed. That is why you should run the rehearsal and read the reconciliation report before deciding.
Is my data sent to anyone else?
Your files are processed by Bakasir's own systems. AI suggestions for column mapping are optional, only available when the platform has enabled them, and require your consent; what is sent is limited to column names and sample cell values, not the whole file or transaction data.
