Skip to content

Switching systems without losing your history

What data to bring over from your old POS or ERP, how to continue your document series and numbers, how long to run both systems side by side, and how to reconcile the numbers to the peso before you turn the old one off.

By Jorge Zamarrón 8 min read

Share Link copied
In this article
  1. What has to come over
  2. Moving to Nori
  3. Both systems at once
  4. Reconciling to the peso
  5. Before turning the old one off

The hard part of changing your point of sale or your ERP is rarely the installation. It shows up a week later, when a customer asks how much they owe and the figure looks nothing like the old system's, or when the accountant asks for a March invoice nobody can find. A good switch gets decided earlier, around three questions: what data comes over, how long the two systems live side by side, and how you prove the numbers are the same.

What has to come over

Not everything weighs the same. Some data stops you on day one if it stays behind; other data you only need to be able to look up.

Customers. With RFC (tax ID), legal name, tax regime, postal code and CFDI use. Under CFDI 4.0 the recipient's name and postal code have to match their tax status certificate, so a customer list with "Walk-in customer" in half the records gets cleaned now or causes trouble on every invoice.

Items. Code, name, barcode, unit, VAT and the SAT product key. Price lists too, because wrong prices are the first thing a salesperson notices.

Stock per warehouse, with its cost. Cost matters as much as quantity: if it comes in at zero, your profit for the first few months comes out inflated.

Every open invoice with its number and balance. A total per customer isn't enough. Aging needs each document's date, and if the invoice was stamped as PPD (paid in installments or later), the payment receipt you issue when the customer pays has to point to that invoice's fiscal folio, even if it was stamped in the old system.

The CFDI XML files. They're part of your accounting records, and the Federal Tax Code requires keeping those for five years. The PDF can be generated again; the stamped XML can't.

Historical documents and payments. You need them to compare sales against last year, to handle a return of something sold before the switch, and to answer the customer who says they already paid.

Series and numbers

If your last invoice was A-4511, the first one in the new system should be A-4512. The SAT no longer requires consecutive numbers (the fiscal folio, the UUID, is what identifies the invoice), but your accountant and your collections team look invoices up by series and number, and so do your customers. Two A-4512 invoices in the same year lead to phone calls nobody wants to take.

In Nori each document series has a Next number, and the Next number preview shows what the next document's number will look like before you save. If the series already has imported documents with higher numbers, Nori takes the next free one and never repeats a number.

The reports people use

This one gets left off almost every list. The manager who checks sales by rep every Monday, or the commissions report someone built years ago with a custom query: if the new system doesn't have them, the team feels something was lost even though all the data arrived.

Make the list before migrating and ask each area what they open every day. In Nori's report designer you build your own reports with a read-only SQL query, with the visual wizard or by describing them to the AI. If you're coming from Nori desktop, .repx files import as they are and Nori translates the query; anything it couldn't convert is flagged Needs review. For the IT team, SQL access includes views with the desktop's table and column names (documentos, partidas, socios…), so their old queries keep running.

Moving to Nori

It depends on where you're coming from.

From Nori desktop. In Administration › Utilities › Migrate from Nori desktop you upload the SQL Server .bak backup and, if you have them, one .zip with the layouts and XML folders and another with the images. Items come over with their prices and stock, partners with their balances, documents from every year with their payments and e-invoices, plus users and print layouts. You run it first with Dry run only: it copies everything to a test database and hands you a reconciliation report without touching your data. The guide Migrate from Nori desktop has the steps.

From another system, without an ERP. Items and customers go in with the Excel template in Set up your company: you upload it, Nori shows you every row with its errors before saving and, if a code already exists, updates it, so you can fix the file and upload it again. For balances, with Nori's accounting you use the opening journal entry, with one line per customer and per vendor so the subledger and aging reconcile. Opening stock goes in with a goods receipt using the opening inventory reason, which posts against Opening balances and not as income.

With SAP Business One or NetSuite. If the ERP stays, so does the accounting history. Nori brings catalogs, balances and credit limits from the ERP and shows them read-only. What changes is the point of sale, and what you need to watch is that Nori's series don't collide with the ones the ERP already uses.

Both systems at once

Running in parallel gives you peace of mind, with two conditions.

First: only one of them stamps. If both registers issue a CFDI for the same sale, you have two live invoices at the SAT and one of them has to be canceled. Decide on day one which system is the official one and, in the other, enter sales without stamping.

Second: it has to last long enough to go through a full month-end close. Before that you can't see the month's collections or stock after a count. After two or three months double entry wears people down, someone stops doing it and the comparison is useless.

One alternative that sometimes works better is running in parallel by branch: one store starts on the new system and the rest stay on the old one. Nobody enters anything twice and problems show up in one contained place.

Old systemEntry without stamping NoriOfficial: the one that stamps Month reconciliationSales with and without taxBalance per customerStock valueCollections by payment form Turn off the oldBackup kept If it doesn't match: explain it and fix it
The old system goes off when the same reports for the same month give the same result in both.

Reconciling to the peso

"It roughly matches" isn't good enough to turn a system off. Pick a closed period, run the same reports in both and compare them line by line:

  • Sales for the period, with and without tax. In Nori's report designer, "Sales by period" counts each sale once (invoices, plus what was delivered and not yet invoiced, minus credit notes and returns) and also shows the subtotal before tax.
  • Each customer's balance, with receivables aging. A grand total that matches can hide two customers with errors that cancel out.
  • Stock value per warehouse. Quantity and cost.
  • Income by payment form, against the register closings. In Nori this report already subtracts the change handed back in cash, so you compare it against what actually came in.
  • Stamped CFDI: how many and for how much. If you keep your books in Nori, the SAT bulk download compares what the SAT has on record as issued with what Nori stamped.

When you come from Nori desktop, much of this is already in the reconciliation report: counts on each side, documents by type and month with their totals, each customer's balance, each item's stock in each warehouse and whether every fiscal folio made it. Differences show in red with a link. If you agree with one, you accept it by writing the reason, and the record shows who accepted it and when.

Many differences aren't migration errors. They're things the old system had been dragging along for years, like lines for deleted items or repeated numbers in a series. Others are a few centavos and almost always come from rounding, because one system calculates VAT per line and the other per document. What matters is that each one has its explanation written down. A difference nobody can explain comes back at audit time.

Before turning the old one off

Keep a full backup of the old system's database and, if you can, leave a read-only installation around for a few months. Keep the XML folder separately too, even if you already uploaded it. In the Nori desktop migration, the files you upload are deleted automatically a few days after it finishes; your backup is the one that stays with you.

And tell your customers if anything changes in what they receive: the invoice layout, the email it comes from or the series. An invoice that arrives looking different with no warning is the one that goes unpaid because someone in accounts payable didn't recognize it.

If you're about to switch, start with the list of reports each area opens every day. It's the part that gets planned the least and missed the most.

Frequently asked questions

Do I have to keep the same invoice numbers in the new system?

The SAT doesn't require it: in CFDI 4.0 the series and number are for internal control, and what identifies the invoice is the fiscal folio (UUID). It's still worth continuing the numbering, because your customers and your accountant look invoices up by series and number, and two invoices with the same number in the same year confuse everyone. In Nori each series has a Next number field so you can start where you left off.

What do I do with the XML files of old invoices?

Keep them. They are part of your accounting records, and Mexico's Federal Tax Code requires keeping those for five years. If you migrate from Nori desktop, the XML folder goes up in a .zip and each XML is linked to its invoice by fiscal folio. The SAT also keeps a copy of everything you stamped, and you can get it back with the SAT bulk download.

How long should I run both systems?

Long enough to go through at least one full month-end close and compare that month's reports. Less than that won't show whether collections and stock reconcile. Past two or three months the team gets tired and double entry starts to slip.

How do I bring in customer balances if I'm not coming from Nori desktop?

With Nori's accounting, you enter them with an opening journal entry, with one line per business partner on the customer and vendor accounts so their subledger and aging reconcile. Opening stock goes in with a goods receipt using the opening inventory reason, against Opening balances rather than as income.

What if I use SAP Business One or NetSuite?

With the ERP connected, catalogs, balances and credit limits come from the ERP and Nori shows them read-only. The accounting history stays in the ERP, so changing your point of sale doesn't move it.

Integration

Share Link copied

Want to see it with your ERP?

In the demo we look at your version, your series and what makes sense to sync.

Request a demo

Keep reading