Guide to migrating company data from Excel to a real ERP

Choosing between off-the-shelf and custom software often starts from a brochure, not from the process. Teams then discover missing steps, shadow Excel and a migration that never finishes. The honest path starts from how work actually runs.

An ERP (or management system) succeeds when the team uses it daily on a clear MVP: less double entry, more reliable times, and parallels turned off on purpose.

Process first, catalogue later

Map the critical flow — orders, stock, invoices or jobs. Write what must improve in ninety days. Compare tools against that perimeter, not against a feature checklist of fifty items.

Migrate one slice at a time. Keep a short parallel only while you validate. If adoption is low, fix friction and training before buying another module.

Vendors and boundaries

If an external vendor enters, clarify who owns configurations, prompts, mappings and logs. Avoid opaque dependencies. A good partner leaves the company more autonomous at ninety days, not more tied to endless tickets to change one rule.

A detail that makes the difference

Block calendar time for the pilot. Without dedicated slots the project stays «between other things» and never really starts. The operating owner updates status every week in five minutes: done, blocked, next step. It is not elegant. It works.

What to leave out on purpose

The first release is not the moment to prove everything the tool can do. Leave out features without an owner, integrations to little-used systems, automations on rare exceptions and aesthetic reports not tied to a decision. Expanding after the numbers is courage. Expanding before is anxiety dressed as ambition.

Dirty data, dirty results

If records and inputs are messy, any automation or language model amplifies the mess. Dedicate an explicit block to minimal clean-up on the MVP perimeter: duplicates, required fields, out-of-range values. That is not «IT work». It is operational truth.

Training that sticks

Short sessions on the team's real cases. A checklist within reach. A super-user per area for the first fifteen days. Avoid catalogue courses that end in a certificate and zero change the following Tuesday.

How you know you are improving

Do not multiply dashboards. Pick a few indicators tied to the process you are touching — on migrating company data from Excel to, cycle time, output quality and adoption of the official flow usually suffice. Set baseline in week zero. Review at thirty days. If numbers do not move, change process and inputs before you change the tool.

After the pilot: expand without losing the thread

Widen only if the primary KPI improved, adoption beats the agreed threshold, the exception backlog is under control and the owner is still in charge. Otherwise reduce scope or strengthen training. A meeting every two weeks is enough: numbers, top exceptions, decisions. No status theatre.

Document the mapping or happy-path rules on a living page. When someone new joins, that page saves three weeks of oral tradition. Light governance is not bureaucracy: it is operating memory.

After the pilot: expand without losing the thread

Widen only if the primary KPI improved, adoption beats the agreed threshold, the exception backlog is under control and the owner is still in charge. Otherwise reduce scope or strengthen training. A meeting every two weeks is enough: numbers, top exceptions, decisions. No status theatre.

Document the mapping or happy-path rules on a living page. When someone new joins, that page saves three weeks of oral tradition. Light governance is not bureaucracy: it is operating memory.

Vendors and boundaries

If an external vendor enters, clarify who owns configurations, prompts, mappings and logs. Avoid opaque dependencies. A good partner leaves the company more autonomous at ninety days, not more tied to endless tickets to change one rule.

A detail that makes the difference

Block calendar time for the pilot. Without dedicated slots the project stays «between other things» and never really starts. The operating owner updates status every week in five minutes: done, blocked, next step. It is not elegant. It works.

What to leave out on purpose

The first release is not the moment to prove everything the tool can do. Leave out features without an owner, integrations to little-used systems, automations on rare exceptions and aesthetic reports not tied to a decision. Expanding after the numbers is courage. Expanding before is anxiety dressed as ambition.

Dirty data, dirty results

If records and inputs are messy, any automation or language model amplifies the mess. Dedicate an explicit block to minimal clean-up on the MVP perimeter: duplicates, required fields, out-of-range values. That is not «IT work». It is operational truth.

Training that sticks

Short sessions on the team's real cases. A checklist within reach. A super-user per area for the first fifteen days. Avoid catalogue courses that end in a certificate and zero change the following Tuesday.

How you know you are improving

Do not multiply dashboards. Pick a few indicators tied to the process you are touching — on migrating company data from Excel to, cycle time, output quality and adoption of the official flow usually suffice. Set baseline in week zero. Review at thirty days. If numbers do not move, change process and inputs before you change the tool.

How you know you are improving

Do not multiply dashboards. Pick a few indicators tied to the process you are touching — on migrating company data from Excel to, cycle time, output quality and adoption of the official flow usually suffice. Set baseline in week zero. Review at thirty days. If numbers do not move, change process and inputs before you change the tool.

After the pilot: expand without losing the thread

Widen only if the primary KPI improved, adoption beats the agreed threshold, the exception backlog is under control and the owner is still in charge. Otherwise reduce scope or strengthen training. A meeting every two weeks is enough: numbers, top exceptions, decisions. No status theatre.

Document the mapping or happy-path rules on a living page. When someone new joins, that page saves three weeks of oral tradition. Light governance is not bureaucracy: it is operating memory.

Vendors and boundaries

If an external vendor enters, clarify who owns configurations, prompts, mappings and logs. Avoid opaque dependencies. A good partner leaves the company more autonomous at ninety days, not more tied to endless tickets to change one rule.

A detail that makes the difference

Block calendar time for the pilot. Without dedicated slots the project stays «between other things» and never really starts. The operating owner updates status every week in five minutes: done, blocked, next step. It is not elegant. It works.

What to leave out on purpose

The first release is not the moment to prove everything the tool can do. Leave out features without an owner, integrations to little-used systems, automations on rare exceptions and aesthetic reports not tied to a decision. Expanding after the numbers is courage. Expanding before is anxiety dressed as ambition.

Dirty data, dirty results

If records and inputs are messy, any automation or language model amplifies the mess. Dedicate an explicit block to minimal clean-up on the MVP perimeter: duplicates, required fields, out-of-range values. That is not «IT work». It is operational truth.

Training that sticks

Short sessions on the team's real cases. A checklist within reach. A super-user per area for the first fifteen days. Avoid catalogue courses that end in a certificate and zero change the following Tuesday.

Training that sticks

Short sessions on the team's real cases. A checklist within reach. A super-user per area for the first fifteen days. Avoid catalogue courses that end in a certificate and zero change the following Tuesday.

How you know you are improving

Do not multiply dashboards. Pick a few indicators tied to the process you are touching — on migrating company data from Excel to, cycle time, output quality and adoption of the official flow usually suffice. Set baseline in week zero. Review at thirty days. If numbers do not move, change process and inputs before you change the tool.

Practical schema to bring to a meeting

Short version to bring to a meeting.

Steps

1. Map critical process + 90-day outcome.
2. Choose MVP features only.
3. Migrate one slice; log exceptions.
4. Shut down shadow Excel on that slice.
5. Review adoption KPIs before expanding.

Quick checklist

• Goal written down.
• Owner active.
• MVP defined.
• Pilot planned.
• KPI baseline set.

KPIs (max three)

• Average process time (before/after).
• Error or rework rate.
• % usage of the official flow.

Practical value (and the next step)

A new ERP is not a feature catalogue: it is a process the team uses every day. Practical value is less shadow Excel, less double entry and more reliable times on orders, stock or invoices.

Start from a measurable MVP, migrate one piece at a time and shut down parallels. If adoption stays low, fix friction and training before adding modules.

If you want a second opinion on the scope of your case, Foggetti Studio can help you read the current state and define a realistic MVP.