CMS battle: Drupal vs. EPiServer

Please note that this article is over 11 years old, so the content and links may not necessarily be up to date. For more recent reading, you might be interested in one of these articles:

Drupal and EPiServer seem to be the most common adversaries in Finland right now when it comes to big website projects. Therefore we decided to publish some comparison slides that help to figure out the main differences between these systems.

North Patrol is a consulting firm specialized in the design of digital services and information systems. We shape ideas into a vision and service concept, find the best architectural and technological solutions, design a functional user experience, and compete to find the ideal partner for implementation work. We do not sell implementation projects, nor do we sell licenses; we are genuinely on the side of the customer.

20 May 2014

Perttu Tolvanen

This article is a part of CMS selection article series by North Patrol. 

North Patrol helps customers to make smart technology decisions and find the best implementation partners. Typically, we facilitate prestudy projects and evaluate vendors and proposals. Most of our clients are large companies headquartered in Finland.

After all, the two systems are quite different kinds of beasts. Especially from the content producer’s perspective it is quite a different thing to do an EPiServer project than a Drupal project. Also living with a commercial product or with an open source ecosystem is quite different story from client organisation’s point of view.

>> Browse the slides in SlideShare

To summarize:

If online service is your core business, Drupal is a strong platform for accelerating your own type of development — even a very unique and magnificent one. It is no coincidence that media companies are big players in the Drupal camp. Drupal’s model is also well applicable to extreme multi-channel publishing and performance.

If your online service is primarily sales and marketing oriented, EPiServer’s product features should get you excited. Web teams producing multi-language marketing sites, in particular, should consider EPiServer as a power tool.

Perttu Tolvanen

Perttu Tolvanen is a web concept design and content management system expert.

Perttu consults with clients on project planning and defining requirements, and supports customers in selecting content management systems and implementation partners. His areas of specialisation include facilitating concept design workshops and selecting content management systems.

Perttu has ten years of experience with web and intranet projects, including serving as a project manager and consultant. Earlier in his career Perttu has worked in procurement and as a project manager at a large media company, a content management system consultant at a large IT company and an independent, neutral consultant at his own firm. He is also a well-known seminar speaker and blogger. Perttu is also the editor of Vierityspalkki.fi, a Finnish blog about the Finnish internet and its creators.

Websites

Building a complex and content-heavy website? North Patrol's team helps you design data structures, user interfaces and key functionalities.

Read about our services

Request a quote

About North Patrol

We’re eight experienced consultants — designers and technology specialists — focused on vendor-neutral, practical results. Every year, we complete 30-40 customer engagements with customer satisfaction at 9.5/10. Clients come to us to make confident decisions and deliver better digital services.

Read more about us

How to work with us

  • Small consulting engagement

    A small engagement is ideal when you need a clear answer to a specific question, a tough decision supported by independent analysis, or simply a quick outside view.

    Pricing is a fixed fee agreed in advance to keep things predictable, and getting started is as simple as sharing your goals and any background material so we can propose a crisp scope and price.

  • Prestudy & feasibility evaluation projects

    A prestudy is the right choice when you are framing a larger initiative, building internal alignment, or testing whether an idea is worth pursuing — for example a platform change, a new digital service, a consolidation effort, or an AI/automation use case.

    In four to eight weeks we interview key stakeholders, map needs, assess the current state across content, architecture, integrations, and governance, and combine vendor‑neutral market insight with technical feasibility and risk analysis.

    We then outline effort, budget, and timeline ranges with clear assumptions and scenarios, and we shape a high‑level solution concept and target architecture sketch.

  • Supervision & quality control for technical implementation

    Independent supervision is most effective when you already have a delivery partner and want oversight that keeps scope, quality, and budget on track.

    We manage risks, provide executive‑level updates, support acceptance testing, and conduct readiness reviews before go‑live.

Back to top