Dynamics 365 Recruiters Who Search the Old Names Too
Thirteen retired product names sit behind Dynamics 365, and plenty of the bench still describes the work as Navision or AX, which is why a clean keyword search walks straight past them. Our first submittals land in two to three weeks.
KORE1’s Dynamics 365 recruiters source and screen Finance & Operations, Business Central, and Customer Engagement talent across the Microsoft partner channel, delivering first qualified submittals in two to three weeks with 92% of placements still in seat a year later.
Last updated: August 31, 2026
A controller at a Midwest distributor called us in the spring about a Business Central lead. Her internal recruiter had run the requisition for seven weeks and produced four people, none of whom had touched a general ledger.
The requisition said Dynamics 365 Business Central. Fair enough. That is the product’s name.
The trouble is that the person she wanted had spent eleven years doing exactly this work under a different label, first on Navision, then on Dynamics NAV, and his profile said so in the plainest possible language. It never once said Business Central, because he had never had a reason to type it. A keyword search does not know those are the same thing. A recruiter who has worked this market does, and that is roughly the whole difference between seven weeks and nine days.
Microsoft has been rebranding this family since it started buying it in 2001. Everyone in the market has quietly absorbed the cost of that except the search tools.
The Right Person’s Profile May Not Contain the Words on Your Requisition
Most enterprise platforms have the opposite problem. Type SAP into a database and you get four hundred people, most of whom sat near a program once. Dynamics under-returns instead. The string is precise, the market’s vocabulary is not, and you end up with a short list that looks manageable and is missing the people you needed.
Three title patterns cause most of it. Long-tenured consultants still describe themselves by the product they came up on. Partner-side developers get titled by the technology rather than the suite, so a Customer Engagement build sits under Power Platform Developer or Dataverse Developer. And in-house people at end-user companies frequently carry a title with no product in it at all, like ERP Analyst or Systems Accountant, because their employer only runs one system and nobody needed to specify which.
Nobody is being cute. It is just what happens when a vendor renames a product line four times inside twenty years, the market keeps using whichever name it learned first, and everybody’s work history stays written in the past tense.
Our strings run the lineage, not the brand. Role definitions, rate bands and the three-cloud breakdown live on the Dynamics 365 consultant staffing page. This page is about how the search itself gets run.
Thirteen Names, One Bench
Four product lineages, every name each one has carried, and roughly when it carried that name. The marked names are the retired ones. They are also the ones a candidate is most likely to have written down, and the ones your requisition does not mention.
Anyone who ran a multi-entity close on AX 2012 can run one on F&O. Half of them have never updated the word.
The deepest Business Central people in the country are former NAV people. The label changed in 2018. Their working vocabulary did not.
This lane is worse than the others, because the current names are ordinary English words. Search Sales and see what comes back.
Microsoft ends Dynamics GP product enhancements, tax updates and technical support on December 31, 2029, with security patches running to April 30, 2031. Every GP shop in the country is about to need somebody who speaks both sides.
Thirteen retired names across four lineages, and every one of them is still load-bearing on somebody’s profile right now. That is the whole reason a Dynamics search benefits from a recruiter who has been in this market a while, more than it does from a bigger database.
Almost Nobody Good Is Between Jobs, Because Dynamics Is a Partner Market
Microsoft does not implement Dynamics. Its partner channel does, and Microsoft says so in its own Dynamics 365 implementation guidance, which points buyers at a reselling partner and describes FastTrack as collaborating with that partner network. So the partner bench is where the experience lives, sitting on utilization targets, booked out weeks in advance, and generally about as available as a good contractor in a housing boom. A consultant who has closed six implementations is not scrolling job boards on a Tuesday night. She is on a client site in Columbus with a go-live in eleven days.
Which changes what a search has to be. Posting reaches the population that happens to be looking, and in this market that skews toward people between partner engagements, some of whom are excellent, some of whom are between things for a reason you would want to know about before the offer goes out. You should not build a go-live team exclusively out of that pool.
So our Dynamics work runs referral-first. When a Business Central consultant we placed in 2024 rolls off hypercare, the call is not a pitch. It is a question about who else on that team is coming free, and it gets a straight answer because there is history behind it. Partners talk. The market is smaller than it looks.
The same model runs across the broader enterprise bench through our ERP recruiters desk, and across the wider technology market through tech recruiters.
Partner-Side and Customer-Side Are Two Different Hires
This is the question we ask on every Dynamics intake call, and it is the one clients least expect. Where has this person been sitting?
Partner-side consultants run eight to twelve implementations in the time an in-house person runs one. They move fast. They have sat through every configuration argument there is, usually more than once, and they are used to handing the finished system over to somebody else and getting on a plane. Customer-side people own a single instance for years. They know the chart of accounts and the three ugly workarounds nobody documented, and they think in quarters rather than in sprints.
Both are good. They fail differently. Drop a partner consultant into a quiet single-instance seat and there is a reasonable chance you lose them around month seven, not because the job was bad but because the variety was the thing they actually liked. Put a lifelong in-house person on a program running four parallel go-lives and the pace does the damage instead.
We ask directly. Then we tell you what we heard. A candidate who says out loud that they are tired of airports is telling you something useful about the next three years, and it should change how you frame the offer. If you want to push on it yourself, the Dynamics 365 interview questions set has the versions of this question that work.
Leadership searches in this space, meaning ERP directors and the people who own the roadmap, run through executive recruiters instead.
Three Ways a Dynamics Search Quietly Stalls
None of these look like a problem in week one. All three show up around week four, which is the expensive place to find them.
The Cloud Was Never Settled
Finance & Operations, Business Central and Customer Engagement have separate talent pools. A requisition that just says Dynamics 365 gets sourced three ways at once and shortlisted zero ways.
The Environment Is a Guess
On-prem AX, a hosted NAV instance and a current online tenant are three different jobs. Nobody asks, and the finalist turns out to have only worked in the one you are leaving.
The ISV Layer Is Invisible
Most real Dynamics estates carry third-party add-ons for warehousing, tax or field service. Those extensions are half the work and they almost never make it onto the job description.
Twenty minutes on an intake call settles all three. If you would rather work through it yourself first, the consultant staffing page carries the full role and rate breakdown, and the Business Central and Dynamics developer pages go a level deeper.
Brief Us Monday, First Names Inside Two Weeks
One Business Central contractor or a seven-person F&O program team, the sequence is the same. What changes is how many people run through it at once.
- 01
Scoping Call
Cloud, environment, version, ISV layer, and whether the seat is partner-shaped or in-house. Half an hour, and it usually surfaces at least one thing the requisition did not say.
- 02
Lineage Sourcing
Every search string carries the retired names alongside the current one. AX and Axapta for F&O, NAV and Navision for Business Central, CRM and Dataverse for CE, GP and Great Plains for the migrations.
- 03
Channel Outreach
Referral-first through consultants we have placed and the partner teams they came up alongside. Most first submittals come from here rather than from a database pull.
- 04
Configured or Attended
Every claim gets a follow-up. Which modules they personally configured, which environment, and one open question about a cutover that went wrong. People who were in the room answer that for six minutes without prompting.
- 05
Runway and Aftercare
Debriefs the same day, feedback inside 24 hours, because your finalists are carrying other processes. Then calls at 30, 60 and 90 days. Month two is the wobbly one and a check-in catches it while it is still fixable.
Demand under all of this keeps climbing. The U.S. Bureau of Labor Statistics projects computer systems analysts, the category that absorbs most ERP functional work, to grow faster than the average occupation through 2034. The Dynamics supply side has not moved at anything like that rate.
Three Ways to Put Dynamics People on the Program
Same recruiters and the same screen underneath all three. What changes is who carries the person.
Contract and Contract-to-Hire
Implementations end, and most implementation seats should end with them. Contract-to-hire fits when you want the person on your side afterward but would rather watch them work a cutover first.
Contract staffing details →Direct Hire
For the roles that outlive the project. The internal Business Central analyst, the F&O functional lead, and whoever owns the environment after the partner packs up.
Direct hire details →Project Team and SOW
A team against a deliverable instead of a set of headcounts. The right shape when a workstream needs owning end to end rather than seats needing filling.
Project staffing details →Common Questions
What does a Dynamics 365 recruiter do that our internal team can’t?
A Dynamics recruiter searches the product lineage rather than the brand name, so AX, Axapta, NAV, Navision, GP and CRM profiles surface alongside current ones. That alone typically doubles the reachable bench on a mid-market requisition.
After that it is reach. The strong consultants sit inside Microsoft partners on utilization, so they are not responding to postings, and getting them on a call is a relationship rather than a campaign. An internal team can absolutely run the logistics of a Dynamics search. Building the shortlist is the part that goes sideways.
How fast can you get us Dynamics 365 candidates?
Two to three weeks to first qualified submittal on standard Dynamics roles. Specialty seats run longer. An F&O warehouse management lead with live WMS experience is closer to a month, because there are not many of them and most are already committed to somebody’s peak season.
We would rather give you a real date on the intake call than a flattering one. If a search is genuinely six weeks, knowing that in week one changes what you decide about interim coverage.
Do you recruit for Finance & Operations, Business Central, and Customer Engagement?
All three, plus the Power Platform work that sits underneath Customer Engagement. We scope every requisition to one primary cloud before sourcing opens, because the pools barely overlap.
Migration searches are the exception worth flagging. A GP to Business Central move needs somebody fluent on both sides, and that profile is genuinely scarce, so those searches get planned earlier.
Which Dynamics 365 roles are hardest to fill right now?
F&O supply chain and warehouse management leads are the tightest, then GP to Business Central migration consultants, then Field Service implementers who can also build in Power Automate. All three are being pulled forward by the 2029 GP deadline.
X++ developers deserve a mention. The pool stopped growing years ago, a good share of it moved sideways into functional or architecture work, and the people still writing X++ every day are mostly inside partners who would very much like to keep them there.
How do you check Dynamics experience before we see anyone?
Every claim gets a follow-up question. Which modules they configured personally, which environment and version, what the ISV layer looked like, and one open question about something that went wrong at cutover.
That one carries the weight. Somebody who lived through a failed data migration will talk about it in specific detail, unprompted, for several minutes, right down to which table blew up and what the CFO said the following morning. Somebody who watched from the next room changes the subject fairly quickly.
We already have an implementation partner. Why would we hire a recruiter?
Your partner staffs its own team, not yours. The client-side roles are still yours to fill, meaning the internal functional lead, the data owner, and whoever runs the system in 2030 once the partner has moved on.
A fair share of our Dynamics placements sit alongside an active partner engagement. Some of them exist precisely because somebody wanted a person in the room whose paycheck came from their side of the table.
What do you need from us before sourcing starts?
Five things: the Dynamics cloud, the environment and version, the ISV add-ons in play, whether the seat is partner-shaped or in-house, and who makes the hiring decision. A half-hour call usually settles all of it.
If a couple of those are still open, say so. Guessing is worse. A search built on a decision nobody has actually made needs rebuilding around week four, and rework is the delay that costs real money.
Send us the requisition. We’ll tell you which name it should also be searching for.
One call is normally enough to settle the cloud, scope the environment, set an honest date, and describe what the bench actually looks like for that seat.
Talk to a Dynamics Recruiter →