Umbraco kind of has this rep as “the friendly CMS”, open source, .NET-based, and flexible enough that, honestly, a lot of developers with .NET experience can get a basic site up and running quickly. But that’s also the thing. The low barrier to entry makes the pool of self-described Umbraco people really huge, and only a smaller slice has actually shipped a complex, business-critical Umbraco setup under real pressure, with data, tight SEO obligations, custom integrations, plus a launch date that cannot drift.
So this guide is meant to show what, in practice, separates a solid Umbraco partner from someone who simply knows the CMS, so you can judge a shortlist without relying on name value alone.
Start with Partner Status, But Don’t Stop There
Umbraco has a formal partner program with three tiers: Silver, Gold, and Platinum. For an umbraco CMS development company, those tiers map to certification levels held by the agency’s team. A Silver partner needs at least one Certified Professional (meaning someone who passed Umbraco’s Fundamentals exam). A Gold partner needs an active Certified Expert. And Platinum needs either a Certified Master or two Certified Experts on staff. Also, certifications do expire after two years, so the partner tier is a decent “current” signal, not a badge they earned once and then just kept.
There’s another label layered on top: the “Contributing Partner” designation. It’s reserved for agencies that actually give something back to the open-source project itself, things like hosting user groups, contributing code, or helping steer new features. That extra cue tends to matter because it often suggests the agency’s more senior folks are engaged with Umbraco at a depth beyond just client delivery.
None of this means you should just filter purely by badge. Partner tier basically tells you an agency has put resources into certification and has a history that Umbraco itself has reviewed. Still, it doesn’t really tell you if they ever handled a setup like yours, you know, the kind that’s not just “a website”: a multi-site layout, a headless delivery, migration off a legacy CMS, and then integration with a specific ERP. So use partner status as the first sift, then do the real digging into what’s relevant for your exact project.
Ask What They’ve Actually Built, Not Just What They Can Build
“ We can build anything in Umbraco “ is the kind of line every agency will throw out, because it’s true in a practical sense; Umbraco is flexible on purpose. But also, it’s not a useful answer. You want specificity, not a slogan:
- Did they deliver something of comparable weight to yours, like content volume, traffic levels, the number of sites or brands involved, basically the same scale and shape?
- Have they migrated a site into Umbraco from some other CMS, and if yes, how did they treat the URL structure and the SEO equity during the switch? Was it careful or more “we’ll figure it out later”?
- Have they worked with Umbraco Heartcore or a headless Umbraco approach, if your work depends on API-first composability rather than a more traditional monolithic build?
- Do they have experience connecting Umbraco with the actual systems your business relies on – CRM, ERP, DAM, even a search platform that already has its own logic and quirks?
An agency that responds with a named project, some real figures, and even a few honest caveats about what didn’t go smoothly is a completely different situation from a team that only answers with capability talk, like it’s a brochure.
Understand Whether You Need a Build, a Migration, or a Modernization
These are three different projects people tend to kind of glue together under the same “Umbraco development” label, but honestly the skill set isn’t the same for each one, not even close. Sometimes it feels like everyone says “we do Umbraco” and then it kinda stops there.
A greenfield build is the easiest case and probably the most forgiving scenario; there’s no legacy content, no existing integrations to preserve, no SEO history to keep safe. Most competent Umbraco shops can manage that pretty well, usually without too much drama.
Then you have a migration into Umbraco from another CMS. This one gets spicy. It involves mapping the old content structures into new ones, preserving URLs and redirects so search rankings don’t tank, and often untangling custom functionality that was created for the old platform and doesn’t have a clean equivalent. In this situation, partner-tier badges matter less than a solid, proven migration process. You want phased content moves, automated testing, and a rollback plan, because mid-cutover things can break in annoying ways.
Next is modernizing an existing, ageing Umbraco site. Think upgrading from Umbraco 7 or eight to a contemporary LTS release, for example. This sits someplace among the alternative two. Technically, it’s a model improvement instead of a whole migration; however, it nonetheless hits content, material models, custom code, templates, and integrations that could have been written years in the past in opposition to an older API. Umbraco 17, launched in late 2025 as the contemporary long-term-supported model running on .NET 10, is now sort of the reference factor; maximum groups are the use of once they pitch enhancements for legacy sites. And an employer that has truly run that precise improvement path, now no longer simply building clean sites, is really worth more right here than a person with an extended customer list, but no actual improvement experience.
So be straight with yourself and be straight with candidate agencies about which of these three you actually need. It changes both the right vendor and the right price, and if you get that wrong, everything downstream gets more expensive.
Look Past the CMS to the Platform Underneath
Umbraco runs on .NET, and honestly, a pretty strong Umbraco agency will usually have real engineering depth in .NET overall, not just someone who’s looked around the back office or knows the templating conventions. It’s this kind of “beyond the surface” thing that starts to matter most when your project is doing anything past straight content management. Like custom business logic, gnarly integrations, performance tuning when there’s real traffic, or even a security posture that has to stand up in an audit, without breaking a sweat.
So yeah, this is a solid moment to widen the angle of what you’re trying to find out about a candidate agency. Instead of just asking “how much Umbraco experience do you have,” you can ask what other Microsoft .NET platform work they actually do. Because a umbraco cms development company that treats Umbraco as one part of a bigger .NET and modernization practice, rather than the only specialty they have, tends to deliver more engineering rigor when the build gets complex and the requirements start moving around. Bits Orchestra is a useful example of that pattern: it’s a software engineering company specializing in the modernization of complex web platforms, CMS, and DXP on Microsoft .NET, with Umbraco as one of several platforms it works across alongside Kentico, Contentful, Sanity, and Strapi. Its approach to composable and headless architecture, breaking a monolithic CMS into separated content, commerce, and presentation layers, with React or Next.js front ends, reflects that. NET-first engineering background rather than a CMS-only skill set. The company has also handled CMS migrations that preserved content, URLs, SEO equity, and integrations through phased cutover and post-launch stabilization, which is the exact discipline a harder Umbraco migration requires.
The thing isn’t that every project needs that kind of depth; a plain marketing site really doesn’t. But if your Umbraco project has integrations, custom logic, or a migration with SEO stakes, then an agency whose Umbraco work lives inside a larger .NET engineering practice is usually better set up, compared to one that only understands the CMS layer, kind of in isolation.
Check How They Handle Risk, Not Just How They Pitch
Agencies are, understandably, better at describing their strengths than their failure modes. And a few practical questions tend to reveal whether you’re dealing with a vendor that has a real process, or one that’s just improvising:
Do they run a paid discovery or assessment phase before they quote a fixed price on anything beyond a simple build? If they skip that step on complex work, they’re often either underpricing (and you’ll see it later as change orders), or they haven’t actually scoped the risk. Also ask what their rollback plan looks like if, after go-live, a migration or upgrade surfaces a critical bug; “we test thoroughly” isn’t a rollback plan; it’s more like a wish. Then ask who stays involved after launch: does a senior architect remain on the hook through stabilization, or does the team move on the same day the site goes live? Finally, ask for a reference you can truly call, not some polished quote from a “results” page, but a real talk with someone who has gone through the mess, and still remembers it clearly.
Weigh Size and Location Against Your Project’s Actual Needs
Umbraco agencies go from small, extremely specialized shops to bigger multinational firms with literally hundreds of developers. A large agency might give you more parallel capacity and wider regional reach, yet a smaller, senior-heavy group often ends up placing more experienced people directly on your project. Not routing you through some account layer, or whatever it’s called.
For Umbraco specifically, geography matters less than it does in some other categories, because most delivery gets done remotely anyway, no matter where their office is located. Still, time zone overlap helps with collaboration, and there’s also that context piece. How comfortable are they with your regulatory or sector environment, like healthcare, financial services, or government, that kind of thing? That can be genuinely worth weighing too.
How They Approach Technical Discovery
One of the more clear-ish ways to judge an Umbraco agency is to look at what happens before development even starts, like really before. A solid agency should be able to translate your requirements into a workable technical blueprint, not just jump straight into “templates” and that kind of page assembly.
In the discovery phase, the team needs to spell out the key building blocks of the whole project: the Umbraco version and underlying architecture, content arrangement, integrations, hosting setup, user permissions, search requirements, and any migration limits. If there’s an existing website involved, they should also review the current CMS configuration and figure out what can move over as-is, what has to be rebuilt, and where custom development will be necessary.
Architecture choices become even more important when the work goes past a normal corporate website. A multi-site installation, for instance, brings up questions like: how exactly does content get shared between the sites, how are domains and languages handled, and can editors operate across several properties without ending up with messy duplication. If you’re going with headless, then there are extra things to think about around APIs, frontend frameworks, caching behaviour, and how content is delivered.
Also, don’t ignore the types of questions the agency brings up here. A seasoned Umbraco team will typically want to know how your content is organized, who actually maintains it, which systems must connect into Umbraco, and what the platform should be able to support later. An agency that only cares about appearance and page volume, like almost entirely, might not be planning far enough forward.
The outcome from discovery should be more than just a list of features. You want to walk away with a proposed architecture, you know, with real shape and not only a vague direction, plus technical risks that are identified early, integration needs spelled out, migration considerations, and also a clear explanation of why the agency recommends a particular approach. Otherwise it’s pretty hard to evaluate. What you get should feel concrete before development starts and, frankly, it makes it way easier to compare agencies on technical competence rather than on presentation alone.
The Real Test
Strip away all the marketing pages, and the agencies worth shortlisting answer the same handful of questions the same kind of way. Like, with a named project, a specific number, and an honest account of what was actually hard about it. If a prospective Umbraco CMS development company can’t point to a migration, integration, or upgrade of comparable complexity to yours, with a client name attached, not just some case study headline, then that’s the signal to trust, not a glossy pitch deck. Partner tier gets you a decent first filter. Then the rest of the choice comes down to whether their real delivery experience lines up with the exact shape of the problem you’re paying them to solve.
