From Symfony, Pimcore or Shopware to TYPO3

A prospective client may never arrive with a brief that says, "We want TYPO3." Instead, they describe the website they need.

It may need to support several brands, websites, markets or languages. Different editorial teams may require carefully controlled permissions and approval workflows. The platform may need to integrate with product data, CRM, commerce or other business systems. It must accommodate a completely custom design, remain maintainable for years and avoid locking the organisation into a proprietary platform.

This is the type of substantial, enterprise-level website for which TYPO3 can be one of the strongest open-source CMS choices.

However, many agencies never include TYPO3 in their evaluation. Not because the platform is unsuitable, but because they do not yet have TYPO3 knowledge inside their team.

As a result, an agency may recommend the platform it already knows rather than the platform that best fits the project. It may try to extend a commerce or data-management system further into content management, build expensive editorial functionality itself or select a CMS that becomes restrictive as the client's requirements grow.

The missing piece is not necessarily a different platform. It is access to the right expertise.

You do not need a TYPO3 department to propose TYPO3

If your developers already work with Symfony, Pimcore, Shopware or another Symfony-based system, adopting TYPO3 is a smaller step than it may first appear.

TYPO3 has its own architecture and CMS-specific concepts, but its modern development environment shares many foundations with the wider Symfony ecosystem: Composer, dependency injection, service configuration, console commands, Symfony routing components, Doctrine DBAL and event-driven extension points.

Your developers are not starting again from zero. With an experienced TYPO3 partner supporting the architecture and the first implementation, an existing PHP team can begin contributing while learning TYPO3's platform-specific concepts in practice.

We believe this is exactly what an official TYPO3 Consultant Partner should do for agencies. Our mission at Digital Zombies is not to replace an agency's developers, designers or client relationships. It is to make TYPO3 a realistic option when it is the right choice for the project.

We provide the specialised knowledge needed to deliver the immediate work, collaborate with the existing team and transfer knowledge so its developers become increasingly confident with TYPO3. This means an agency can pursue the right enterprise opportunities without hiring an entire TYPO3 department before accepting its first project.

When does TYPO3 belong on the shortlist?

Not every website needs an enterprise CMS. TYPO3 becomes particularly compelling when the complexity is not limited to the frontend. It deserves serious consideration when a project includes several of the following:

multiple websites, brands, business units or regional presences;
multilingual content and localisation workflows;
editors with different roles, permissions and responsibilities;
review and approval processes before publication;
structured content that must remain consistent across a large platform;
custom integrations with business systems and external services;
a long expected platform lifetime;
requirements for extensibility and controlled, maintainable releases;
a preference for professional open-source software and reduced vendor lock-in.

TYPO3 was built for content-rich environments in which governance matters as much as publishing. Multisite management, localisation, granular access rights and workspaces are not afterthoughts that an agency must recreate for every enterprise project.

At the same time, TYPO3 is highly extensible. It can serve as the content platform within a wider technical ecosystem rather than trying to replace every specialised business system around it. That distinction is important for agencies already working with Pimcore or Shopware.

Pimcore can remain responsible for product information, digital assets or master data. Shopware can remain the commerce platform. TYPO3 can take responsibility for complex editorial experiences, corporate content, multiple sites and the workflows surrounding them. The right architecture does not force one platform to solve every problem.

From an unfamiliar CMS to an adjacent capability

For an agency already building with Symfony-based platforms, TYPO3 should not be viewed as a completely separate technical world.

A Pimcore team understands Composer projects, Symfony services, controllers, events and structured data. A Shopware team understands Symfony-based extension development, dependency injection, console commands and complex integrations. A Symfony application team already works with many of the underlying components TYPO3 uses. Several technical concepts will feel familiar from the beginning.

Composer-based project management

Professional TYPO3 projects are installed and maintained with Composer. Dependencies are explicit, extensions can be packaged cleanly, and project configuration belongs in version control. For teams accustomed to Symfony, Pimcore or Shopware, this is normal application development — not a CMS maintained through manual uploads and production-side changes.

Dependency injection and services

TYPO3 uses Symfony's DependencyInjection component and supports service configuration through Services.yaml. Constructor injection is the recommended approach. Developers can continue to write focused, testable services with explicit dependencies. The surrounding conventions are close enough to Symfony for the mental model to transfer quickly.

Console commands

TYPO3 uses the Symfony Console component for command-line functionality. Custom commands for imports, synchronisation, scheduled processes and maintenance tasks use an API that Symfony-oriented developers already recognise.

Routing

TYPO3 adds CMS-specific responsibilities such as page-based URLs and route enhancements, but its frontend routing is implemented using Symfony routing components. The platform introduces a content-aware layer without abandoning familiar technical foundations.

Doctrine DBAL

TYPO3 provides database connections and a QueryBuilder based on Doctrine DBAL. Developers with Doctrine experience will recognise the style, even though TYPO3 does not reproduce a typical Symfony-and-Doctrine-ORM application architecture.

Events and extension points

TYPO3 provides PSR-14 events for extending core and third-party behaviour. The API differs from Symfony's EventDispatcher, but the architectural principle is familiar: react to defined events through listeners rather than changing core code.

These similarities do not make TYPO3 identical to Symfony, Pimcore or Shopware. They make it approachable.

Custom design without giving up a mature CMS

One persistent misconception about enterprise content management systems is that stronger editorial capabilities inevitably mean less creative freedom. That does not have to be the case with TYPO3.

TYPO3 does not dictate how a website should look. Its Fluid templating system gives frontend developers the flexibility to implement a completely custom design, while TYPO3 manages the content, permissions, localisation and editorial workflows behind it.

Reusable content elements can be designed around the project's visual language instead of forcing the design into a predefined theme or generic page builder. Editors receive practical flexibility, while the design system provides the guardrails needed to maintain consistency across the website.

We have seen this work particularly well when collaborating with design- and UX-led agencies. In one such project, the agency created the complete design and user experience, while Digital Zombies handled the TYPO3 implementation. We translated the agency's design into reusable Fluid components and editor-friendly content elements without diluting the intended experience.

The division of responsibilities worked naturally. The agency retained ownership of strategy, design and the client relationship. We provided the TYPO3 architecture and development expertise behind the delivery. The result was not a compromise between a custom website and an enterprise CMS. It was a custom digital experience supported by a mature content platform.

Fluid and Extbase provide a structured way to build

Design freedom is only useful when the implementation remains maintainable.

Fluid is TYPO3's templating engine. It supports layouts, templates, partials and reusable ViewHelpers, giving frontend developers a structured way to translate a component-based design into TYPO3.

For custom application functionality, Extbase provides TYPO3-oriented MVC concepts such as controllers, repositories, domain models and validation. It is not Symfony, and developers should not try to force Symfony patterns into every TYPO3 problem. But experienced PHP developers will recognise the separation of responsibilities and find many of the concepts approachable.

TYPO3 also does not require every custom feature to use Extbase. Developers can work directly with TYPO3's core APIs and services when that is the better architectural choice.

The important point is that custom TYPO3 development can follow the same engineering values a strong Symfony team already applies: separation of concerns, explicit dependencies, code review, testing, version control and automated deployment.

Knowledge can be transferred — not kept behind a wall

Our second agency experience demonstrates why that familiarity matters.

The agency had TYPO3 projects to maintain and extend, but no longer had sufficient TYPO3 capacity internally. We initially provided the specialist knowledge and delivery capacity needed to keep those projects moving.

Our role went further than completing tickets. We worked alongside the agency's developers, explained the relevant TYPO3 concepts and conventions, reviewed implementations and helped them understand the existing codebase. Because the developers already had solid PHP and Symfony-related experience, they could connect unfamiliar TYPO3 concepts to engineering principles they already knew.

Over time, they could begin contributing rather than remaining permanently dependent on an external TYPO3 team.

This is an important consideration for agency and technology leaders. Bringing in a specialist partner should not mean creating a new black box. The partner should protect the immediate delivery while also making the agency's own team more capable.

What your developers will still need to learn

It would be misleading to suggest that Symfony experience removes the TYPO3 learning curve entirely. Developers will encounter platform-specific concepts:

TCA defines how records are structured, displayed and managed in the TYPO3 backend.
TypoScript configures content rendering and aspects of site behaviour.
Fluid replaces the Twig-based templating approach familiar from Symfony platforms.
Extbase provides a TYPO3-specific MVC framework for extension development.
Site packages and extensions contain project-specific configuration, presentation and functionality.
The page tree, workspaces, permissions and localisation model reflect the requirements of editors and larger organisations.

These concepts are not unnecessary obstacles. They are part of how TYPO3 solves content-management problems that a bespoke Symfony application would otherwise need to solve itself.

The fastest route is not to translate every familiar convention literally. It is to understand which principles transfer directly, which TYPO3 APIs should be used and where the CMS already provides the right abstraction. That is where experienced guidance makes the greatest difference.

A practical way to evaluate TYPO3

An agency does not need to commit a major client project to an unfamiliar platform without first testing the fit. A focused technical evaluation can be small enough to complete without creating a long internal initiative:

Select a realistic enterprise brief or a contained part of an upcoming project.
Identify the requirements that genuinely need a CMS: content structure, languages, permissions, workflows and integrations.
Install a current TYPO3 project with Composer.
Build a site package rather than modifying third-party code.
Implement one real design component as a custom, editor-friendly content element.
Add a small service, integration or console command.
Let both developers and editors evaluate the result.

This reveals much more than a generic product demonstration. It shows whether TYPO3 fits the agency's development practices, how much design freedom it retains and what the editorial experience can become when it is deliberately designed.

With a TYPO3 specialist involved, the evaluation can also establish a sound architecture instead of producing a proof of concept that later needs to be discarded.

What an official TYPO3 Consultant Partner should do

For us, being an official TYPO3 Consultant Partner is not simply a credential. It describes the role we want to fulfil in the ecosystem.

Agencies should be able to propose TYPO3 when it is the right platform for their clients — even when they do not yet have all the necessary experience internally.

Our role is to close that gap. We can support an evaluation, shape the architecture, implement the project, maintain an existing platform or work behind the scenes as part of the agency's delivery team. Just as importantly, we share our knowledge so the agency's developers can take on more responsibility with confidence.

The immediate goal is a successful project. The longer-term goal is a more capable and confident agency team.

If your agency works with Symfony, Pimcore, Shopware or another modern PHP platform, TYPO3 may be much closer to your existing capabilities than you think. And if an enterprise brief looks right for TYPO3 but the missing expertise is holding you back, that is exactly the conversation we would like to have.

Considering TYPO3 for an enterprise project?

Talk to Digital Zombies about the project, the technical requirements or a focused TYPO3 evaluation.

Start the conversation

The Enterprise CMS Your Symfony Team May Already Be Ready For