Everyone tells you to get off Excel. Nobody tells you how to do it without losing a month of work, corrupting your opening balances, or ending up with a system half your staff quietly refuses to use. Here is the honest, step-by-step version, from someone who has done the migration many times.
Almost every serious business in Pakistan started on Excel, and honestly, that was the right call. Excel is free, everyone half-knows it, and for the first few years it bends to whatever you need. The trouble is that it never tells you when you have outgrown it. There is no alarm. One day you simply notice that three people are maintaining four spreadsheets that no longer agree, that the stock sheet and the sales sheet tell different stories, and that closing the month has become an act of faith. That is the moment people start looking at ERP, and it is also the moment the fear kicks in.
The fear is reasonable. Everyone has heard the horror story: a business that switched systems, lost a month to the changeover, corrupted its opening balances, and ended up with staff quietly keeping their old Excel files on the side because they never trusted the new thing. That does happen. But it happens for predictable reasons, and every one of them is avoidable. A migration is not a leap of faith, it is a sequence of careful steps in the right order. Get the order right and it is almost boring. Get it wrong and it is exactly the disaster you were afraid of.
Before the how, it is worth being honest about the why, because it explains where migrations go wrong. People stay on Excel not because it is good, but because it is theirs. They know exactly where every number is. They can change anything in a second. There is no login, no permission, no waiting. An ERP feels like handing that control to a machine that will not let them just overtype a cell when they are in a hurry. That instinct, the fear of losing control, is the real reason migrations fail, far more than any technical problem.
Which means a good migration is as much about trust as it is about data. The job is not only to move numbers from spreadsheets into a database. It is to get to the point where your team opens the ERP first thing in the morning instead of the Excel file, because they have seen it be right, again and again, with their own eyes. You do not win that trust with a big-bang switchover and a training session. You win it by running both systems side by side until the ERP has quietly proven itself. More on that in a moment.
Key insight
The first real step is master data: your list of items, your customers, your suppliers, your chart of accounts. Everything else in the system points back to these, so they go in first, and they need to be reasonably clean. This is the stage where the accumulated mess of years on Excel comes to light, the same product spelled three different ways, one customer entered as four, items with no proper category. Migration is the moment to fix that, because you are touching every record anyway.
The key word, though, is reasonably. Do not fall into the trap of trying to make your master data flawless before you start, or you will never start. Clean the obvious duplicates and the worst inconsistencies, get it good enough to work with, and refine the rest as you go. A good ERP helps here rather than fighting you. In NavoBook we deliberately built the import step to be forgiving, you bring in your items, customers and suppliers from a spreadsheet using a sample template, and the system matches against what already exists instead of blindly creating duplicates, so a name that differs only by capitalisation or spacing does not silently become a second record. The tool does some of the cleaning for you, which is exactly what you want when you are staring at years of Excel.
Watch out
If master data is where migrations get messy, opening balances are where they get dangerous. Your opening balances are the financial snapshot of your business on the day the new system takes over: how much cash and bank you have, what stock is on hand and at what cost, who owes you money and how much, and who you owe. Get these right and the ERP starts life reconciled to reality. Get them wrong and every report the system ever produces is built on a crooked foundation, and you will spend months chasing differences that were baked in on day one.
The two things people botch most are stock and receivables. Stock has to come in not just as quantities but at proper cost, because that cost is what the system will use for every future sale and every profit calculation. Receivables and payables have to come in invoice by invoice where it matters, not as one lump sum, otherwise you can never match a customer’s payment to the actual bill it was for. This is fiddly, unglamorous work, and it is precisely the part you do not rush. A clean opening balance is worth a week of care, because it saves you a year of confusion.
Real scenario
| Step | What goes in | Why in this order |
|---|---|---|
| 1. Master data | Items, customers, suppliers, chart of accounts | Everything else refers to these, so they go in first and clean |
| 2. Opening balances | Cash, bank, stock on hand, who owes you, who you owe | This is your starting line, the day the new system takes over |
| 3. Open items | Unpaid invoices and bills still to be settled | So receipts and payments can be matched against real dues |
| 4. Go live | New transactions entered in the ERP from a fixed date | One clean cut-off, not a slow blur of two systems |
| 5. Parallel run | Old and new kept side by side for a few weeks | You trust the ERP once it matches, then you drop Excel |
A migration needs a clean line in the sand. You choose a date, load your opening balances as of that date, and from that day forward every new transaction goes into the ERP. What you do not do is enter some sales in the new system and some in the old one because it was quicker, or backfill three months of history “to be safe.” That blur, where reality is split across two systems, is what makes a migration drag on for months and leaves nobody sure which number to believe. One date, one cut-off, held firmly.
The start of a month is the natural choice, because it lines up with how you already close your books and file with FBR. You are not trying to reconstruct years of history inside the new system; you are drawing a line and moving forward from it. Your old Excel files stay exactly where they are as a record of the past. The ERP owns the future. Keeping that boundary crisp is one of the simplest, most underrated things you can do to make the whole change go smoothly.
For the first few weeks after going live, keep doing a little of what you did before, in parallel. Enter your transactions in the ERP, but also keep the key Excel figures updated, and at the end of each week compare them. Does the ERP’s cash balance match what you counted? Does its stock figure match the floor? Do its receivables match what customers actually owe? Every time the two agree, your team’s trust in the new system grows a little. This is not wasted effort, it is exactly how the fear gets replaced with confidence.
Then, at some point, you stop. Once the ERP has matched reality for a few weeks running, the Excel files have made their point and you let them go. This is the step nervous businesses skip, they run parallel forever, hedging, and never fully commit, which means they never get the real benefit of the ERP and just carry the cost of maintaining two systems. Parallel running has a purpose and an end. Use it to earn trust, and then trust. The whole point was to get off Excel; do not stop one step short.
Key insight
The last thing worth saying is that migration is one of the few parts of running a business where outside help genuinely pays for itself. Someone who has moved dozens of businesses off Excel knows the order to do things in, knows where opening balances go wrong, and knows how to import your data without creating a duplicate mess. That experience is the difference between a migration that takes a week and one that limps along for months. It is why we include implementation and onboarding rather than handing you a login and wishing you luck.
And it connects to the bigger reason for switching in the first place. Excel does not just get slow as you grow, it stops telling you the truth, because nothing reconciles and everything can be quietly overtyped. The point of moving to a real system is to get one set of numbers that agree, the theme running through our guide to choosing ERP software in Pakistan. A migration done in the right order is simply how you get from the world of four disagreeing spreadsheets to the world of one number you can trust. It is worth doing, and it is worth doing carefully.
If you have outgrown Excel but the thought of switching is holding you back, that hesitation is healthy, it just means you want it done properly. Talk to us about what your spreadsheets look like today, and we will walk you through exactly how we would move your items, customers, suppliers and opening balances into NavoBook, in the right order, with a clean cut-off and a parallel run so your team trusts it before you let Excel go. NavoBook is one plan, PKR 30,000 a month, all 18 modules included, with implementation and onboarding handled by our team, not left to you. The details are on our pricing page.
All 18 modules. PKR 30,000/month. No hidden per-module fees. Start today.