Choosing an implementation partner usually starts with a few emails.

You explain that you’re considering Business Central. The partner schedules a meeting. Then comes the presentation.

Microsoft credentials. Experienced consultants. Successful projects. Customer logos. A few screenshots.

After sitting through several of these meetings, you can end up wondering how you’re supposed to tell them apart.

The answer usually isn’t in the presentation.

You learn much more when you start talking about the awkward parts of your business.

Show Them What Your Team Actually Deals With

Don’t give the partner a cleaned-up version of your company.

Show them the real thing.

If your accounts team exports numbers to Excel every month because the current reports aren’t enough, mention it. If somebody in the warehouse keeps a notebook beside the computer because they don’t trust the stock figures, mention that too.

Even the little things can matter.

Maybe one employee has built a spreadsheet that everyone depends on but nobody officially owns. Maybe sales has a strange process for handling special orders. Maybe your purchasing team has to enter the same information in two different places.

These are not embarrassing details.

They are clues.

A good consultant will usually want to know why those workarounds exist. What problem were they solving? Who depends on them? Could the process be improved instead of simply copied into the new system?

That conversation tells you more than another hour of slides.

Ask About Similar Businesses, Not Just Big Numbers

A partner can tell you they have completed a large number of Business Central implementations.

Fine.

Now ask how many looked like yours.

A company with several legal entities has different concerns from a small single-location business. A manufacturer has different requirements from a professional services company. A business with an ecommerce site and warehouse software has another layer of complexity.

Be specific when you ask about experience.

Don’t stop at “Have you done manufacturing?”

Ask what they implemented. Ask what the difficult part was. Ask what their team was responsible for.

And if they offer a customer reference, use it.

Ask the customer what they would do differently if they started the project again.

That answer can be more useful than hearing another list of success stories.

Find Out Who Will Be There After the Contract Is Signed

There is a simple question worth asking before you agree to anything:

Who is actually doing our implementation?

The senior people involved in the sales process may not be the people working on your system every day.

Ask to see the project team.

Who handles the finance setup? Who deals with data? Who builds integrations? Who handles custom development? Who is managing the schedule?

You don’t need to know every person’s job title.

You need to know who owns each important piece of the project.

And if the answer is “we’ll decide later,” ask why.

Take a Hard Look at Your Old Data

This part is rarely as clean as people expect.

An old database can contain years of duplicates, old customer records, unused item numbers, incorrect addresses, incomplete information, and transactions that nobody wants to touch.

Moving all of it into Business Central isn’t really a solution.

First decide what needs to come across.

Then find out how the partner plans to get it there.

Ask about field mapping, cleanup, validation, and test migrations. More importantly, ask who is expected to review the results.

Your implementation partner can tell you whether a field migrated successfully.

Your employees are usually the ones who can tell you whether the information makes sense.

Both sides matter.

Pay Attention When You Ask for a Custom Feature

At some point, somebody on your team will say:

“We need Business Central to do it exactly like the old system.”

Maybe you do.

Maybe you don’t.

The partner shouldn’t simply agree because it makes the sale easier.

Ask what the existing process is actually accomplishing. Then ask whether Business Central can handle it another way.

There are times when custom development is completely reasonable. There are also times when a company spends money recreating an old workaround that it would have been better off abandoning.

The useful partner is the one who can explain that difference.

Don’t Let the Cheapest Proposal Make the Decision

Price matters, but the headline number doesn’t tell the whole story.

Open the proposal and start looking at what is included.

Migration. Integrations. Reports. Testing. Training. Project management. Go-live assistance.

Then look at what isn’t included.

This is where you should ask the slightly uncomfortable questions.

What if the data needs more cleanup?

What if the integration takes longer than expected?

What if users discover something important during testing?

You want to know how changes will be handled before they become an argument about additional fees.

A detailed proposal may actually save you from a lot of confusion later.

Ask Them to Explain Testing in Plain English

“Testing is included” sounds reassuring, but it doesn’t tell you much.

Ask what your employees will actually do.

Will finance run through a normal month-end?

Will sales process a complicated order?

Will the warehouse test receiving and shipping?

Will someone deliberately test an integration failure?

Those questions matter because a system can look fine during a demonstration and still cause problems when people start using it for real work.

Your employees should get their hands on the system before launch.

They will notice things the implementation team may not have considered.

Training Needs to Be About Jobs

People don’t really learn an ERP by watching someone click through twenty slides.

They learn it by doing the work.

The finance team should practice the transactions they perform. Warehouse employees should work through the activities they handle. Sales staff should use realistic customer scenarios.

Give them time.

If someone gets confused during training, that’s useful information. You still have time to fix the process or explain it differently.

Finding the same confusion after go-live is much more painful.

Ask About the First Few Weeks

Go-live gets a lot of attention because it has a date attached to it.

The days immediately afterward matter just as much.

People will have questions. Someone will forget how to complete a transaction. A report may need a small adjustment. An integration may behave differently with a particular record.

Ask the partner what happens when that occurs.

Who do you contact?

How quickly are urgent issues handled?

How long does the implementation team remain available?

And if you want more development or improvements later, can the same team continue helping?

You want those answers while everyone is still sitting around the table—not after something has already gone wrong.

Give Them a Problem They Can’t Solve With a Slide

If you’re serious about choosing between partners, give the finalists the same real problem.

Use something your business genuinely struggles with.

Don’t make it a theoretical exercise.

Explain the situation and see what questions they ask.

A consultant who takes ten minutes to understand the problem before suggesting anything may be giving you a better sign than someone who has an answer in thirty seconds.

Listen for the details.

Do they notice dependencies? Do they question assumptions? Do they explain the downside of an option as well as the upside?

You are not just buying Business Central knowledge.

You’re bringing another team into your business.

Final Thoughts

There is no single question that will tell you which Business Central partner to choose.

Look at experience. Check the proposal. Understand the team. Discuss migration, integrations, customization, testing, training, and support.

But spend just as much time watching how the partner behaves during those conversations.

Tell them what is messy.

Tell them what doesn’t work.

Tell them what your employees have been doing to get around the limitations of the current system.

Then listen.

The partner that takes the time to understand those problems—and is willing to tell you when an idea may not be the best approach—will give you a much clearer picture of what working together could actually look like.