Getting Off Excel: How to Migrate Oil & Gas Operations to an ERP Without Stopping Production | Blog

# Getting Off Excel: How to Migrate Oil & Gas Operations to an ERP Without Stopping Production

TL;DR: Migrating from Excel to an ERP in Angola's oil and gas sector doesn't happen in a weekend or in one "big bang" — it happens domain by domain, starting with an honest inventory of what actually exists, running a defined parallel-operation period, and closing with a rigorous reconciliation of opening balances, all while production keeps running.

If you run upstream operations, a supplier base in Angola, or a production unit's warehouse, chances are a meaningful part of the business still lives in Excel files — stock reconciliation sheets, preventive maintenance trackers, joint interest billing (JIB) worksheets, HSE incident logs. That's not incompetence: it's what happens when a business grows faster than the systems supporting it. The problem is that, starting in 2026, Angola stopped tolerating that slack. Mandatory electronic invoicing and SAF-T (AO) file submission, under Presidential Decree No. 71/25 of 20 March, already apply to large taxpayers, State suppliers, and any taxpayer issuing invoices valued at or above 25 million Kwanzas — a group that covers essentially every mid-size-and-up operator, EPC contractor, and oilfield services company (EY Angola).

Wise Hustlers builds and operates its own ERP for the energy sector, covering upstream, wells, production, projects and contracts, procurement, suppliers, inventory, MRO, maintenance, fleet, logistics, HSE, quality, HR, training and finance. This guide is deliberately practical: what to inventory, in what order to migrate, how to run parallel operation without duplicating work, and how to close opening balances without surprises at the first audit.

Why "just move everything into the ERP" never works

The temptation with an ERP project is to treat it as a technical migration: export from Excel, import into the ERP, delete the spreadsheets. In practice, three things consistently go wrong when this is attempted all at once.

Historical data is dirty, and nobody knows exactly how dirty. Warehouse spreadsheets accumulate years of manual corrections, inconsistent units of measure (the same material tracked in "boxes" on one sheet and "units" on another), duplicate material codes created because someone couldn't find the original, and stock adjustments made directly in a cell with no record of why. This only surfaces when you try to load the data into a system that enforces referential integrity — and by then it's too late to renegotiate the timeline.

Entire processes exist only in one person's head. In nearly every modernization project we see, there's a warehouse supervisor, a maintenance technician, or a finance clerk who is, in effect, the system. They know the "official" stock sheet is the version in the Downloads folder, not the one on SharePoint. They know supplier X's invoice only gets paid after a verbal confirmation from the field supervisor, even though that's written down nowhere. When that person goes on leave, or leaves the company, the process disappears with them — and the gap only shows up when the ERP asks for a rule nobody can explain.

Pressure to move fast creates shortcuts that get expensive later. It's tempting to migrate everything at once to "get it over with." It is also the shortest path to unplanned downtime — a procurement module error blocking a critical MRO parts requisition, or a wrong inventory balance halting a production order.

Step 1: An honest inventory of what actually exists

Before any conversation about ERP platforms, do a census — not of the systems the business "should" have, but of what it actually runs on today. For a typical Angolan oil and gas operation, this usually spans these domains:

Domain	What usually lives in Excel	Typical risk
Production and wells	Daily production logs, downtime, well tests	No auditable history for ANPG/JV partner reporting
Procurement and suppliers	Supplier master, ANPG certification status, quotes	Uncertified suppliers slipping past local-content controls
Inventory and warehouse	Stock sheets, critical materials lists	Divergence between physical warehouse and recorded balance
Maintenance and MRO	Preventive maintenance plans, failure history	Unplanned corrective maintenance from missed alerts
Billing and JIB	Joint interest billing reconciliation between operators	Partner disputes from lack of traceability
Finance and tax	VAT worksheets, invoice preparation, export files	Inability to generate SAF-T (AO) and AGT-certified invoices on time
HSE and quality	Incident logs, audits, certifications	Loss of compliance data during staff turnover

For each domain, record three things: who actually owns the process (not the org-chart owner, the de facto one), what the current source of truth is, and which business rules exist nowhere in writing. This inventory is the single most important document in the project — more important than the platform choice — because it's what determines the migration sequence and surfaces where the "only in someone's head" processes are hiding.

Step 2: Migrate by domain, not in a big bang

With the inventory done, resist the pressure — internal or from the ERP vendor — to switch everything on at once. Our recommendation, tested building systems for operations that cannot stop, is to migrate by business domain, in an order that respects real dependencies:

1. Master data first — suppliers, materials, cost centers, well/asset structure. Without this clean and de-duplicated, every downstream domain inherits the error.

2. Inventory and warehouse — because this is the domain where physical balances can be counted and verified independently of the legacy system.

3. Procurement and [local content](https://wise-hustlers.com/blog/conteudo-local-angola-anpg-software-conformidade) — linking each supplier's ANPG certification status directly to the master record, so the exclusivity, preference, or competition regime set out in Presidential Decree No. 271/20 is applied automatically at requisition time (CMS Law).

4. Maintenance and MRO — usually the domain with the most tribal-knowledge processes; it benefits from parts inventory already being stable from the previous step.

5. Finance, billing, and tax — deliberately left until after operational domains are stable, because it's the domain most directly exposed to the legal obligation for electronic invoicing and SAF-T (AO), and where an error has a direct regulatory consequence.

Each domain gets its own "go live" cycle, rather than one single cutover weekend. That means more total project months, but it drastically cuts downtime risk — and lets you correct your data-reconciliation approach midway, based on what went wrong in the first domain.

Step 3: The parallel-operation period

No domain should switch systems overnight. Once the ERP is configured and data migrated for a given domain, run both sources in parallel — Excel and ERP — for a defined period before switching off the spreadsheet.

The right parallel-run duration varies by domain; there is no single rule:

Inventory and warehouse: at least one full physical count cycle (typically a month), to confirm ERP movements reconcile against the physical stock count.
Maintenance: at least one full preventive maintenance cycle, to validate that ERP alerts fire at the same points the old plan predicted.
Finance and billing: one complete fiscal month, including close, to confirm VAT worksheets and the data needed for SAF-T (AO) come out of the ERP correctly before the spreadsheet stops being the safety net.

During this period, someone has to explicitly own comparing the two sources line by line — not just the totals. It's manual work, it's tedious, and it's exactly what stops a small discrepancy from turning into a JIB dispute with a partner six months later.

Step 4: Reconciling opening balances

The most delicate moment in any migration isn't go-live — it's the day opening balances are locked in the new system and the old spreadsheet stops being edited. Errors here propagate forward indefinitely.

In the most sensitive domains, three rules are worth enforcing:

Inventory: a full physical count, not an extrapolation from old records. Every divergence between the physical count and the spreadsheet is investigated and documented before being posted into the ERP — never simply "adjusted" to make it match.
Finance: opening balances for payables, receivables, and fixed assets are reconciled line by line against the last valid close, with sign-off from whoever confirms each balance — typically the finance lead, not just the implementation team.
Contracts and JIB: billing balances between operators are confirmed in writing with partners before the ERP becomes the source of truth, to avoid disputes over which system "is right."

Only after this signed-off reconciliation should the old spreadsheet be archived — never deleted, since AGT and joint-venture partners may request the history.

Timelines and costs: our own estimates

There is no reliable market-wide figure for "how much it costs to migrate from Excel to ERP in Angolan oil and gas" — it depends on the number of domains, the state of the data, and the size of the operation. What we can share are our own estimates, as Wise Hustlers, based on how we scope this kind of project:

A single-domain migration (for example, inventory and warehouse, for a mid-size operation) typically takes 8 to 14 weeks, including the initial inventory, configuration, data migration, and a month of parallel run.
A full program covering the seven domains above, done in phases rather than as a big bang, tends to run 9 to 18 months, depending on how many domains can run in parallel with each other without competing for the same internal team.
The most underestimated cost isn't the ERP license or the integration work — it's the operational team's own time spent on reconciliation and parallel-run validation. That should be budgeted as internal effort, not treated as "free" because it doesn't show up on a vendor invoice.

These are our own estimates for planning purposes, not a market average or a fixed-timeline promise — every operation has its own level of data mess and reliance on tacit knowledge.

Where legacy modernization fits in

Much of this work — the technical inventory, designing the domain-by-domain migration sequence, building the data bridges between the old Excel files and the new ERP, and validating the reconciliation — is exactly the scope of our legacy modernization service. We don't sell a single ERP platform; we help design and execute the transition from what already exists, including the less visible work of cleaning historical data and capturing processes that currently live only in one person's head.

Worth saying plainly: several ERP platforms are genuinely well suited to the oil and gas sector, each with different strengths. SAP S/4HANA tends to be the choice for large, complex operators who need native hydrocarbon accounting and joint-venture accounting. Oracle ERP Cloud fits well for organizations already on an on-premise Oracle base looking to move to the cloud without losing that foundation. Microsoft Dynamics 365, with its Oil & Gas layer, tends to fit mid-size operations already embedded in the Microsoft ecosystem. The platform choice is a separate decision from the migration discipline described in this guide — and it's that discipline, not the platform, that this article is about.

Frequently Asked Questions

Can an Excel-to-ERP migration be done without stopping production?

Yes, as long as it's done domain by domain with a parallel-operation period — never switching off the old spreadsheet on the same day the ERP goes live for that domain. Avoiding the "big bang" approach is precisely what prevents downtime.

How long does the parallel-operation period typically last?

It varies by domain: one full physical count cycle for inventory, one full preventive maintenance cycle for MRO, and one closed fiscal month for finance. These are the minimum windows we use on our own projects — never less than one complete operational cycle of the domain in question.

Does Angola's mandatory electronic invoicing directly affect this kind of migration?

Yes. Presidential Decree No. 71/25 makes electronic invoicing mandatory from 1 January 2026 for large taxpayers, State suppliers, and taxpayers issuing invoices at or above 25 million Kwanzas, requiring invoicing software certified or validated by AGT — which means the ERP's finance module has to be ready to issue and communicate electronic invoices, and to generate SAF-T (AO), before that domain goes live (EY Angola).

What if a supplier isn't yet ANPG-certified when we migrate the procurement module?

The ERP's supplier master record should reflect the actual certification status, including suppliers still in the certification process — the statutory deadline for ANPG to complete certification is 180 days after documents are submitted (PwC Angola). Migrating the procurement module shouldn't wait for 100% of suppliers to be certified — but the system needs to clearly flag each one's status, so local-content rules are respected at requisition time.