September 23, 2026

Cloud ERP Five Years Later: What Companies Wish They Had Known

Five years after a cloud ERP implementation, most companies aren’t thinking about whether moving to the cloud was the right decision. They’re thinking about what they would do differently if they were implementing it today.

That’s because an ERP implementation rarely happens under ideal conditions. There are deadlines to meet, business operations to protect, employees to train, integrations to rebuild, and years of data and processes to manage.

So, companies make compromises.

They migrate data they aren’t sure they’ll need. They recreate familiar workflows because users already understand them. They install replacements for old add-ons. They adopt standard security roles because redesigning permissions would take more time. And they automate processes without first asking whether those processes still make sense.

The system goes live. Everyone moves on.

Five years later, some of those hasty decisions start to show up.

The good news is that go-live wasn’t your last opportunity to get the ERP right. In fact, after several years of real-world use, you might be in a better position to optimize it than you were during implementation.

Here are five places to start:

How to optimize your cloud ERP after go-live

Cloud ERP optimization starts by revisiting the decisions made during implementation. After several years of real-world use, organizations should reevaluate data quality, security roles and permissions, legacy customizations, business processes and automation, reporting, and system integrations to determine whether the ERP still reflects how the business operates today.

1. Your ERP doesn’t need to be a museum of your old data

One of the hardest decisions during an ERP migration is deciding what data to bring with you.

When there is uncertainty, the safest answer can seem to be “everything.”

Years later, companies might find themselves maintaining old customer and vendor records, obsolete items, inactive accounts, duplicate records, historical transactions, unused fields, and inconsistent master data that no longer provides much business value.

Beyond filling up your storage, poor-quality data can affect reporting, search, analytics, integrations, and automation.

Five years into your cloud ERP journey, revisit your data strategy:

• Identify which master records are inactive or duplicated.
• Standardize naming and classification conventions.
• Review which historical information must remain readily accessible versus what can be archived, based on business and regulatory requirements.

Then look beyond the ERP.

Has the organization added CRM, eCommerce, warehouse, planning, expense, payroll, or other applications since implementation? If so, determine which system should own each type of data and how changes should flow between systems.

This not only reduces your database storage requirements but also makes the information more accessible to your users and, especially, to automated systems.

2. Reassess ERP roles, permissions, and security

Security and permissions often receive enormous attention immediately before go-live—and not always for the right reasons.

The priority is often focused on making sure everyone can do their jobs on Monday morning.

Default roles get assigned, and then permissions are broadened when users encounter roadblocks. Employees change roles, but their permissions aren’t always updated to reflect their new assignments. New employees inherit access privileges that were created for someone else. Temporary exceptions are never revisited and become permanent.

Five years later, the ERP’s access model might bear surprisingly little resemblance to the company’s organizational structure.

This is a good time to revisit ERP security from first principles.

Start with roles rather than individuals. What should someone in accounts payable, purchasing, warehouse operations, sales, or financial management actually need to see and do? Where should duties be separated? Who can create vendors, change bank information, approve purchases, post transactions, issue credits, or modify sensitive financial data?

Then compare that model with actual permissions.

This isn’t just an IT exercise. Finance, operations, HR, security, and business leadership should participate because access reflects business responsibility and risk, not merely system configuration.

And be sure to make regular security reviews a priority. Employee and organizational changes make periodic access reviews essential.

3. Reevaluate legacy ERP customizations and add-ons

Stop rebuilding your old ERP inside your new ERP.

This might be one of the most expensive implementation mistakes.

During migration, users understandably ask: “How do I do what I used to do?”

That question can drive companies to recreate familiar screens, reports, workflows, customizations, integrations, and add-ons in the new ERP.

It makes the transition easier, at least at first. But taken too far, it can result in a modern cloud platform running yesterday’s business processes.

Five years later, it’s worth inventorying every customization and add-on and asking why each one exists:

• Does it address a genuine competitive or regulatory requirement?
• Does the current ERP now provide that capability natively?
• Is the add-on still supported and valuable?
• Was the customization built because the old system couldn’t handle a process that the new platform handles differently?

Most importantly: If you were designing this process today, would you still design it this way?

Don’t eliminate customization simply for the sake of being “standard.” Some custom capabilities create genuine business value. The objective is to distinguish strategic differentiation from historical baggage.

4. Optimize business processes before you automate them

Don’t automate a process you should eliminate.

If a process is inefficient, automation only makes that inefficient process run faster.

Imagine an old purchasing process that requires information to move through spreadsheets, emails, manual approvals, duplicate data entry, and several handoffs. Moving those same steps into automated workflows might reduce some manual effort, but it doesn’t necessarily make the underlying process more efficient. In fact, automating a process without optimizing it first will only make bottlenecks more pronounced.

After several years in the cloud, take a fresh look at your most frequently used workflows.

Start with the outcome rather than the existing procedure:

• What is this process supposed to accomplish?
• Which steps add control or value?
• Which steps exist because of an old system limitation?
• Where is information entered twice?
• Where do employees leave the ERP and use email or spreadsheets to finish the job?
• Where do approvals sit unnecessarily?

Then simplify before automating.

The best automation projects often begin by removing steps rather than automating them.

5. Revisit ERP reporting, KPIs, and decision-making

ERP implementations tend to produce long lists of reporting requirements.

Five years later, some of those reports have never been opened. Instead, your employees have created dozens of spreadsheets outside the ERP to answer questions no one anticipated during implementation.

It’s time to revisit those reports and KPIs you thought you needed. Look at how your managers actually run the business today:

• Which reports are used? Which are ignored?
• What information gets exported to Excel every week?
• Which numbers require manual reconciliation?
• What questions still require contacting another department for an answer?

Then redesign reporting around decisions rather than reports.

After five years, you know far more about what people actually need than you did at go-live.

Bonus: Reevaluate your ERP integrations

Your application landscape probably hasn’t stood still.

New eCommerce platforms, CRM systems, warehouse technologies, analytics tools, banking applications, industry solutions, and other systems might have been added since your ERP implementation, and integrations might have accumulated over time.

Eventually, nobody is looking at the architecture as a whole.

Now is a good time to map it again.

Identify which applications exchange data, the direction of information flow, which system owns each data element, where duplicate information is maintained, and where manual intervention still bridges gaps.

You might discover that an integration created five years ago is no longer necessary or that a new integration could eliminate an entire manual process.

Your cloud ERP implementation isn’t finished

The most important lesson five years after a cloud ERP implementation might be that an ERP should never be treated as a finished project.

Business processes change. Employees change. Customers change. Technology changes. And cloud ERP platforms continue to gain capabilities after implementation.

Modern ERP platforms such as Microsoft Dynamics 365 Business Central are designed to add capabilities through regular updates. Business Central receives two major release waves each year, with continuous updates between them. This creates an opportunity to periodically reconsider what the platform can do today, rather than assuming the system is limited to what it did at go-live.

Capabilities across Business Central and the broader Microsoft ecosystem, which includes Power BI, Power Automate, Power Apps, and Copilot, also create options that might not have existed when your organization originally implemented its ERP.

Start by asking, “If we were implementing the ERP we already own today, knowing everything we’ve learned over the last five years, what would we do differently?”

You might find that the next major improvement to your ERP doesn’t require replacing anything.

It simply requires taking a fresh look at what you already have:

• Review your data
• Reassess permissions
• Challenge customizations
• Simplify processes before automating them
• Rebuild reporting around the decisions people make today
• Reevaluate your integrations

Get more from the ERP you already have

Your ERP shouldn’t be frozen in time since you went live. As your business, processes, and technology change, you have opportunities to improve your data, security, workflows, reporting, integrations, and use of automation.

Contact ArcherPoint by Cherry Bekaert today. We can help you take a fresh look at your Business Central environment, identify what’s no longer working as well as it could, and find practical ways to get more value from the platform you already own.

Trending Posts