Who is an ERP Functional Analyst?

A good ERP Functional Analyst is much more than someone who knows how to click around an ERP system. 

The role sits at the intersection of business processes, technology, data, communication, and project management and people who are genuinely strong in all of those areas are relatively rare.

Here are the biggest reasons:

1. The skill combination is unusual

A strong functional analyst needs to understand:

• Accounting and finance
• Sales and order management
• Purchasing
• Inventory
• Manufacturing or distribution
• Warehousing
• Supply chain
• Reporting and analytics
• ERP configuration
• Data migration
• Integrations
• Testing
• User training
• Business process improvement

Most candidates are strong in only one or two of these areas.

The really valuable person can say:

“I understand what the business is trying to accomplish, I understand how the ERP works, and I can translate between the business and technical teams.”

That’s a rare combination.

2. ERP knowledge is highly specialized

Someone with five years of experience in one ERP isn’t necessarily transferable to another.

For example, a person who knows Microsoft Dynamics 365 Business Central extremely well may not immediately understand SAP, Oracle, Infor, or Odoo.

Even within Business Central, someone who is excellent at Finance may have limited knowledge of Manufacturing, Warehouse Management, or Service Management.

3. Many candidates are “system users,” not analysts

This is one of the biggest problems.

Someone might have:

10 years of ERP experience

but their actual experience may be:

Enter orders → run reports → troubleshoot user issues → escalate problems.

That’s very different from:

Analyze business requirements → redesign the process → determine ERP functionality → configure the solution → identify gaps → design integrations → develop test scenarios → lead UAT → train users → support go-live.

The second person is a true functional analyst.

4. Good analysts understand the why, not just the how

A mediocre analyst says:

“Business Central can’t do that.”

A good analyst asks:

“Why do you need to do that?”

Then they may discover that the business requirement can be achieved through standard functionality using a completely different process.

That’s a critical ERP skill.

5. Communication is surprisingly difficult to find

The analyst has to communicate with:

Executives ↔ Managers ↔ End users ↔ Developers ↔ IT ↔ Vendors ↔ Consultants

And each group speaks a different language.

For example, a CFO might say:

“I need better visibility into profitability.”

A developer needs something much more precise:

“Calculate gross margin by customer, item, location, and posting period using these specific dimensions.”

The functional analyst translates the first statement into the second.

6. ERP implementation experience is different from ERP support experience

This distinction is extremely important when hiring.

Someone who has spent 10 years supporting an ERP may be excellent at:

• Troubleshooting
• User support
• Issue resolution
• System administration

But implementation requires additional skills:

• Requirements gathering
• Fit-gap analysis
• Process mapping
• Configuration
• Data migration
• Integration analysis
• Testing
• UAT
• Cutover
• Change management
• Go-live

You need to know which type of experience you’re actually hiring for.

7. The best analysts often leave the analyst market

There’s a natural career progression:

ERP Analyst → Senior ERP Analyst → Functional Lead → Solution Architect → ERP Manager → ERP Director

So once someone becomes exceptionally good, they may no longer be applying for “Functional Analyst” positions.

That creates a strange hiring problem: the better the person is, the less likely they may be searching for an analyst job.

8. Companies often create unrealistic job descriptions

This is another major reason.

A job posting might ask for:

Business Central + Finance + Manufacturing + Warehouse + EDI + Power BI + SQL + integrations + project management + 10 years of experience

and then offer compensation appropriate for a mid-level analyst.

That’s essentially asking for a Senior Functional Consultant/Solution Architect while calling the position an analyst.

The result is a tiny candidate pool.

9. ERP functional talent is often industry-specific

A Business Central analyst who has spent years working with:

Manufacturing → BOMs → routings → MRP → production orders → capacity planning

may not be the right person for:

Distribution → warehouse → lot tracking → EDI → 3PL → transportation

Even though both candidates may call themselves “Business Central Functional Analysts.”

10. The best candidates have scars

This is perhaps the biggest difference.

A truly experienced ERP analyst has probably experienced:

• A failed data migration
• Bad master data
• A broken integration
• An incorrectly designed posting setup
• Users rejecting a new process
• A failed UAT cycle
• Scope creep
• Customization that became technical debt
• A go-live crisis
• A vendor misunderstanding the requirement
• A business process that looked good on paper but failed operationally

Those experiences create judgment.

And judgment is difficult to teach.

What I would look for instead of simply “years of ERP experience”

For a Senior ERP Functional Analyst, I’d weight candidates approximately like this:

And I would not automatically reject someone because they don’t know your exact ERP.

A strong ERP analyst with deep process knowledge can often learn another ERP faster than an ERP-specific “power user” can learn how to analyze business processes.

The real definition of a great ERP Functional Analyst

I’d summarize it this way:

A great ERP Functional Analyst understands the business deeply enough to challenge requirements, the ERP deeply enough to design practical solutions, and technology well enough to communicate effectively with developers while being able to get users through the change.

That’s why they’re so hard to find.

And in my view, the biggest hiring mistake is screening primarily for ERP product experience rather than functional problem-solving ability.