Moving to Finocket from Zoho, Odoo, Vyapar, myBillBook, Busy, Marg, Swipe, QuickBooks or a spreadsheet starts in Settings → Import & migrate. Each source has a card: how to export from it, which records come across in this version, what is coming next, and what is deliberately left behind. Tally has its own guided import — see Move your Tally books across. This page covers the mechanics every source shares; your source's own export menu path, spelled out step by step, is on its own page — start at Pick where your books live today.
What comes across today
Parties (customers and suppliers, with GSTIN, PAN and state), items (with HSN, unit, rate and opening stock), your chart of accounts (groups and ledgers), ledger opening balances, and from a spreadsheet-shaped export your invoices with their lines, supplier bills, payments and journal vouchers (a Day Book or manual-journal export, one row per ledger line). What a source cannot bring yet, its card says, rather than implying it works.
Your team can come across too — pick "Team" as what the file holds and a sheet of names, emails and roles invites each one for real, right then. An address that matches somebody already on your team updates their role instead of duplicating an invite; a seat your plan does not have room for is flagged on the dry run, never silently skipped or invited past your limit.
The five screens
Pick. Say what the file holds — parties, items, chart of accounts, groups, contacts, deals, your team, invoices, bills, payments or journals — and choose the file. A party can also come in as a lead, with neither a customer nor a supplier role until you convert it, and a deal's stage is matched against your own pipeline's stages by name — a stage name that does not match is flagged rather than silently landing on your first stage. CSV, XLSX and XLS all work, and so does a Tally-format XML (Tally's own All Masters export, or the Export to Tally that Vyapar, myBillBook and Book Keeper write): its masters are read directly and you go straight to the dry run. A Tally Day Book export (Display More Reports → Day Book → Export → XML) brings the vouchers from your cut-over on — sales, purchases, receipts, payments and journals — and lists, by reason, the ones it does not: cancelled, optional, dated before the cut-over, or in a foreign currency. Coming from Zoho? Drop the whole backup zip that Zoho's own Data Backup page downloads: every file in it we recognise — contacts, vendors, items, the chart of accounts, invoices with their items, bills, payments, journals — is read, and the rest is listed by name. Coming from Odoo? Drop the zip that Manage Databases → Backup downloads: contacts, the chart of accounts, items, sales invoices and purchase bills are read straight off the database backup, no per-module export needed (payments and journal entries still come across as a CSV export, for now). The file is read on your device; nothing is uploaded at this point. A title block above the header is skipped automatically.
Map. Columns are matched to fields by their headers; anything unmatched gets a drop-down. Required fields are marked, and you cannot continue until each has a column. The mapping is remembered for files with the same columns. A column with nowhere standard to go can be matched to one of your own custom fields, or you can create a new one right there — its type is guessed from the column's own values but always shown for you to confirm before it is saved.
Dry run. Every record gets a verdict — create, update, already here, or blocked — and every issue is grouped by what is wrong: a missing group, an invalid GSTIN, a duplicated SKU, openings that do not balance. Blocked rows can be downloaded with the line number and the problem. Nothing has been written.
Import. Pressing Import is recorded as your decision. Records land in small batches, each checked against what is already in your books, so a retry never doubles a record. If you close the page, the rest finishes in the background — the screen checks on its own and updates the moment it is done, and you get a notification either way. A batch that stops on a data problem can be retried right there without starting the import over; it picks up from where it stopped rather than reapplying what already landed.
Reconcile. Your old books' figures beside Finocket's: opening debits equal opening credits, trial-balance totals when your export carried them, and whether every party, item and ledger found a place to land. A line without a source figure is marked not checked — never passed. If anything was blocked or flagged, a link opens that run's own review queue — every affected record, why, and a place to skip it or accept it as it landed. Nothing there is edited on your behalf; a value that needs correcting is fixed in the source file and brought across in a new import.
Bringing the same file twice
A record that already came across from the same source is skipped, not created again. A file that was already imported is refused with the earlier import named, so an export cannot land twice by accident.
Undoing an import
Every import in the history has Undo this import while it stands. It removes what the import created — documents first, then parties, items and ledgers — and keeps, with the reason, anything your business has since built on: a customer who has a new invoice, a ledger with later postings, a record dated inside a locked period. The result says how many came out and how many stayed. An import can be undone once.
What is deliberately not copied
Filed GST returns, IRNs and e-way bills belong to the portal that issued them. Bank-statement matches, attached files and each product's own print layouts are not copied either. The card for each source lists what it leaves behind.