Service pillar
Symfony developer for PHP applications and WordPress integration
Plan Symfony workSend me the system details.
Include the Symfony and PHP versions, the systems the application talks to, the hosting setup and the errors you have already seen in production.
- IntegrationsWP, ERP, CRM
- SyliusB2B commerce
- API PlatformREST and GraphQL
- Upgrades6.4 to 7.4 LTS
Where Symfony fits
I recommend Symfony when the application carries business logic that WordPress and Laravel handle less well: strict types across the codebase, a domain model with clear module boundaries, a long-running integration between WordPress and an ERP or PIM, or B2B sales on Sylius. For a company website or a blog, WordPress costs less to run and is easier for editors, and I say so before I quote.
What I work on
API Platform services with REST and GraphQL, Sylius extensions for B2B catalogues and price lists, Messenger handlers that sync orders and stock with SAP, Microsoft Dynamics or Salesforce, Mercure for live updates in the browser, EasyAdmin or Sonata back offices, and migrations from Zend Framework, CakePHP or Yii to Symfony 7.4 LTS.
What I avoid
I do not propose Symfony for marketing sites or simple content sites; WordPress serves those better. I also do not join a Symfony team as an extra pair of hands without a defined module I am responsible for, a deployment plan and a clear line between my code and theirs.
How does an upgrade between Symfony major versions work?
I move one major version at a time, always starting from the last minor release of the old line: 5.4 before 6.0, 6.4 before 7.0, 7.4 before 8.0. Everything a new major removes is already marked as deprecated in that last minor. In the dev environment the web debug toolbar shows those notices, and symfony/phpunit-bridge, installed with composer require --dev, prints a summary of them after the test run. Rector has Symfony rules that fix part of the code automatically, and I read every line it changes. Once the list is empty, I raise the constraints in composer.json, read UPGRADE-X.0.md for backward compatibility breaks and run composer recipes:update so the config files match the Flex recipes. The server has to keep up as well: Symfony 7.4 needs PHP 8.2 and Symfony 8 needs PHP 8.4.
What do you check when taking over a Symfony application?
First the versions: which Symfony branch the code runs on, when its support ends according to the official release page, and which PHP version the server has. Then composer audit, which lists installed packages with published security advisories. doctrine:migrations:status shows whether the production database matches the migrations in the repository; a gap usually means someone changed the schema by hand. In Messenger I look at the configured transports, whether a failure_transport exists and what is waiting in it (messenger:failed:show). Then the tests: whether they exist, whether they pass and what they cover. Last, configuration: which environment variables production needs, and whether passwords sit in the Symfony secrets vault (secrets:list shows their names) or in a .env file committed to Git. You get the findings in writing, with the risks ordered by severity.
How does Symfony work with WordPress and WooCommerce?
In most projects I join, WordPress stays where editors work, WooCommerce takes the orders and Symfony runs next to them as a separate application. API Platform serves data to a mobile app or a partner portal without loading WordPress. A Symfony integration layer moves orders, stock and prices between WooCommerce and the ERP, puts each message on a Messenger queue and retries it when the other system does not answer, so checkout does not wait for the ERP. When a B2B shop needs customer price lists and approval steps, Sylius, which is built on Symfony, is often a better base than WooCommerce with a long list of plugins. Drupal and TYPO3 also run on Symfony components, so the same knowledge carries over when one of them is the system on the other end.
Frequently asked questions
When is Symfony better than Laravel?
When the code needs strict types and clear module boundaries, when Messenger does a large share of the work asynchronously, or when Sylius or API Platform is already part of the system. Laravel runs production applications just as well; I choose by the team that will maintain the code and the systems the application has to talk to.
Do you work with Sylius?
Yes. Sylius is an open-source e-commerce framework built on Symfony, and I use it for B2B shops: plugins for catalogues and price lists, custom checkout steps, ERP integration and the shop front end.
Can you integrate WordPress with Symfony?
Yes. WordPress keeps the content, and a Symfony service sits between it and the ERP, CRM or PIM. That service validates every message against an agreed format, so a change in one system cannot break the other without anyone noticing.
Do you take pure Symfony work?
Yes, when the scope is written down and the system is one I can understand end to end. Most of my Symfony work is connected to WordPress or WooCommerce, but I also take on standalone Symfony applications that have a clear business purpose.
What about API Platform?
API Platform is part of my work. It builds REST and GraphQL APIs on top of a Symfony domain layer, with serialization, validation and JSON-LD output already in place. I use it when other applications read the data, for example a mobile app or a partner's system.
Explore other WordPress services and knowledge base
Strengthen your business with professional technical support in key areas of the WordPress ecosystem.
Custom WordPress engineering and architecture.
Scalable headless, ERP, and AI architecture for enterprise.
Stores, checkout flow, and sales logic.
Stability, updates, and post-launch support.
What the monthly care fee covers and what changes it.
Business process automation around WordPress and company systems.
Headless WordPress, Sanity, Strapi, and Contentful with Astro or Next.js.
Astro, MDX, edge delivery, and Core Web Vitals measured on real traffic.
Related categories
Supporting articles

How to start as a WordPress developer in 2026. Local environment, theme and plugin development, REST API and headless paths, security and Core Web Vitals. A practitioner playbook that does not waste your first month.

WordPress 7.0 with AI Client vs Astro 6 after Cloudflare acquisition. Speed, cost, SEO and security comparison. My take after 20 years as a WP developer - when to migrate and when to stay.

WordPress 7.0 with AI Client against Astro 7 with the Rust compiler and Vite 8. Speed, cost, SEO and security compared, plus the real bill for my own Astro 6 to 7 migration.
Related services
Senior Symfony developer: upgrades to 7.4 LTS, API Platform services, Sylius B2B shops, Messenger integrations between WordPress and an ERP, and legacy PHP.
Send me the system details.
Include the Symfony and PHP versions, the systems the application talks to, the hosting setup and the errors you have already seen in production.
Plan Symfony work