Migrating from Excel to a Real Invoice System Without Breaking Your Monthly Close

It's the 24th of the month. You're thinking about finally moving off the Excel file you've been using to track invoices for the last three years — the one with 47 tabs, color-coded rows that only you remember the meaning of, and a pivot table that broke last October and never quite got fixed. Month-end is in six days. The SAF-T deadline is in two weeks.

And every time you open a new invoice tool's landing page, the same question stops you: if I start migrating now, will I still be able to close the month?

This is the real reason most accountants and small businesses stay on Excel years longer than they should. Not because Excel is better. Because the switching cost looks existential — and our complete guide to invoice automation maps out what a proper system actually does so you can compare honestly.

It isn't. But you have to do the migration in the right order, and there are three days of the month where you absolutely should not start.

What "Migrating" Actually Means Here

Migrating from Excel to a proper invoice system is not one task. It's four:

1. Getting your historical data somewhere accessible (not necessarily into the new tool).
2. Changing how new invoices enter the system from this point forward.
3. Rebuilding the reports and views you relied on in Excel.
4. Telling the people around you — clients, colleagues, the tax accountant if it's not you — about the new process.

The mistake most people make is trying to do all four at once, the week before the SAF-T deadline. That's how you end up missing the deadline.

Split them. The historical data can wait. The new-invoice pipeline and the reports cannot.

Why Excel Breaks Eventually

Before the migration plan, the honest version of why Excel stops working. Because some people read "move off Excel" content and think it's condescending. You're not dumb for using Excel — Excel is genuinely powerful, and for the first 50–80 invoices per month, it's fine.

It breaks at three specific points:

Multi-client volume. If you're an accountant juggling 15 clients, each with their own Excel file, you're maintaining 15 slightly-different schemas. One client renamed a column. Another added a tab. Consolidating anything across clients takes an afternoon.

Duplicate detection. Excel cannot tell you "you've already entered this invoice" unless you build the formula yourself — and you didn't, because nobody does. Duplicates slip through until SAF-T validation catches them, and by then it's a correction filing.

The person who built it leaves. Every Excel-based accounting workflow has exactly one person who actually understands it. When that person is on holiday, or leaves, or is just too busy that week, the spreadsheet becomes a black box.

If none of these apply to you, don't migrate. Stay on Excel. Come back when they do.

The Migration Plan That Doesn't Break the Month

Assume you're reading this sometime between the 15th and the 25th of the month. That's the right window to plan. The wrong window to start execution is the 1st–12th, because that's when you're closing the previous month and submitting SAF-T.

Here is a six-week migration plan that preserves every monthly close.

1. Week -2: Pick the tool, don't migrate anything

Two weeks before you intend to cut over, pick the tool. Do not touch your live data yet.

What to verify before committing:

• It exports SAF-T in a format AT accepts.
• It imports your existing Excel files (or at least CSV exports) without manual column-mapping on every file.
• It works with Portuguese invoice formats specifically — NIF validation, IVA rates, decimal commas, the works.
• You can export your data back out if it doesn't work. This is non-negotiable. If there's no export, the tool is a trap.

Run the free trial with last month's data — the month you already closed. You're not migrating yet; you're stress-testing.

2. Week -1: Set up, run in parallel for the current month

Create your workspace in the new tool. Configure clients (or your own business), tax rates, supplier list.

Then, for the current month only, enter new invoices in both Excel and the new tool. Yes, it's duplicate work. It's duplicate work for one month. You're verifying the outputs match before trusting the new system with the filing.

This is the step everyone wants to skip. Don't. The week you skip this is the week you discover the new tool is classifying reverse-charge VAT differently than Excel did, and you learn about it from the tax authority.

3. Day 1–12 of the next month: Close the current month on Excel

Do not migrate during close week. Submit SAF-T from whichever system you've been using longest — likely Excel. Your new tool is still in shadow mode.

After submission, compare. Did the new tool produce the same numbers? If yes, you're ready to cut over. If no, figure out why before moving on.

4. Day 13–25: Cut over

This is the calm week between the submission deadline and month-end. The lowest-stakes window in the month. This is when you flip the switch.

From this day forward:

• New invoices only enter through the new tool.
• The Excel file is read-only. Nobody adds rows anymore.
• If you need to reference historical data, you open the Excel file — but you do not edit it.

Tell anyone who interacts with the data: clients who upload invoices, colleagues who enter data, whoever receives the SAF-T output.

5. Next SAF-T cycle: Close on the new tool

The following month's close happens entirely in the new system. Generate SAF-T, validate, submit. This is the first real test.

Keep the Excel file accessible for 12 months. Not for data entry — for lookup. Invoices from October 2025 that you need to reference in May 2026 still live there.

6. After the second clean close: Optional historical import

Only now, with two clean SAF-T cycles in the new tool, consider importing historical data. Often, you don't need to. You need the data accessible, not inside the new system. A read-only Excel file in Google Drive, tagged and organized, is accessible enough for the 2% of the time you need to pull an old invoice.

If you do import, import the current calendar year. Not the last five. Nobody needs 2021 invoices in the new tool.

What to Watch For During the Switch

Three specific failure modes that catch people mid-migration:

Supplier NIFs in different formats. Excel doesn't care if you stored NIFs as "507123456" in one row and "507 123 456" in another. The new tool probably does. Clean these in Excel before exporting, not after importing.

Reverse-charge VAT on EU invoices. If you were handling IVA autoliquidação manually in Excel, the new tool does it differently. Verify on three test invoices before the cutover, not during the SAF-T file generation.

The one client who won't adapt. There's always one. They've been emailing you a monthly spreadsheet for five years and they will continue to, regardless of your new system. Build a lightweight ingest for that client rather than fighting them. One exception is fine. Ten is not.

What to Do Differently

The shift isn't Excel → SaaS. That framing leads to migration anxiety.

The actual shift is: data entry stops being a human task, and the month-end close stops being a bottleneck. In Excel, someone types invoices for four hours, reconciles for three, and the SAF-T deadline is stressful because everything happens in the last week. In a proper system, invoices enter continuously, duplicates get flagged at entry time, and the SAF-T submission is a ten-minute task.

You're not migrating software. You're migrating a habit.

If you're closing a month on Excel and reading this, pick the cutover date now — the 13th of next month, after SAF-T is submitted. Then pick the tool this week. Run it in parallel for the final Excel month. You'll be on a proper system by the following submission, without a single late filing in between.

For the full Excel vs. proper-system comparison, including when Excel is still the right answer, see Faturiza vs Excel. If you're an accountant handling multi-client migration, the accountant-first workflow is built for this exact scenario — and our post on the accountant-client invoice handoff covers how to bring clients along during the switch.

Part of our invoice automation guide series.