--- title: PHP platform migration & modernization description: Apidemia homepage - an overview of the company, its migration approach, and links into services, knowledge base, and contact. --- # Your competitors' engineers just got faster. Yours can't Every month your legacy PHP code costs you more. We migrate it before it becomes a risk - incrementally, with your system running throughout, first results in 4–6 weeks - onto a codebase your team can finally use modern AI tooling on. - Twenty years of PHP - our engineers have built on - and migrated away from - every generation of it. - Official Laminas commercial vendor - one of a short list endorsed by the technology's stewards. - We deliver with AI agents - Claude Code and equivalents, under human review - it shows up in your price. - US and EU contracting entities - Delaware and Romania - contract wherever procurement needs. ## One-minute risk check Which of these sound like your business? Tick everything that's true - nothing is stored or sent. - Changes that used to take days now take weeks, and estimates keep slipping. - Your developers get little useful out of AI coding tools on this codebase. - Only one or two people really understand it, and you'd be exposed if they left. - A customer security questionnaire, insurer, or auditor has raised questions about it. - It can't connect to the tools the business now needs - payments, CRM, reporting, AI. - Hiring or replacing people who can work on it is slow and expensive. - You've been putting off a decision about it for more than a year. Most of the businesses that call us recognize three or four of these. The pattern matters more than any single item. ## Your system works. That's exactly why it's holding you back Nothing is on fire, so nothing gets decided. But most teams running an aging PHP platform recognize several of these at once - and they compound. Afraid to touch the code, end-of-life frameworks, slow feature releases, outdated PHP versions, growing security risks, key developer dependency, shrinking talent pool, rising maintenance costs, performance issues, hard to scale, AI tooling produces nothing useful. ## Is this your platform? If you're running any of these, migration is a matter of 'when,' not 'if'. Each is end-of-life, effectively unsupported, or has no viable upgrade path on modern PHP. ### Legacy CMS & site builders - Drupal 7 - end-of-life. Security risks and an outdated architecture. - Joomla 3 - deprecated, replaced by Joomla 4/5. - WordPress (older installs) - legacy plugins and themes nobody maintains. ### E-commerce - Magento 1 - end-of-life, no official support, and it's handling payments. - OpenCart (older versions) - limited compatibility with modern PHP. - PrestaShop (legacy) - difficult upgrade paths, tightly coupled code. ### Frameworks & custom apps - Zend Framework 1 - deprecated. Replaced by Laminas, now retiring in turn. - CodeIgniter 2/3 - outdated architecture, limited modern features. - CakePHP 2 - legacy conventions and structure. ### Forums & community - phpBB (older versions) - dated UX, limited integration support. - vBulletin (legacy) - old PHP stack, usually replaced rather than upgraded. ### CRM & ERP - SugarCRM Community Edition - discontinued and no longer maintained. - vtiger CRM (older versions) - limited API and integration capability. ### Apigility & API layers - Apigility / Laminas API Tools - end-of-life. We migrate these to Dotkernel API. - Laminas MVC - retiring upstream. A headless move now avoids doing it twice. Not on the list? Most of what we migrate is custom - applications written in-house over ten or fifteen years that were never a product at all. The platform matters less than the condition it's in. ## The cost of standing still Aging software rarely fails. It just quietly gets more expensive. There's no outage and no crisis, which is why it stays on the agenda for years without moving. Meanwhile, four things get worse every quarter. - **Revenue - slower time to market.** Every feature costs more than the last. Competitors on newer systems ship in the time it takes you to scope. - **Deals - failed due diligence.** Enterprise buyers, insurers, and acquirers ask about your stack. "It's old but it works" is no longer an acceptable answer. - **People - key-person risk.** The knowledge lives in a small number of heads. When one leaves, the size of the problem changes overnight. - **Margin - rising cost to run.** Maintenance absorbs budget meant for growth, and the share going to keeping the lights on only climbs. ## AI coding tools rewarded every business with a modern codebase. Yours didn't qualify Teams using agents like Claude Code have changed what a normal delivery pace looks like. The gains are real, and they land almost entirely on code that is modern, tested, and conventional. Point the same tools at a fifteen-year-old system and you get very little, or you get risk. - **The gap widened - standing still now costs more than it did.** The distance between you and a competitor on a modern stack used to grow slowly. Since agents became standard tooling, it grows faster: they get a multiplier on every engineer and you don't. Nothing about your system got worse. The benchmark moved. - **The maths changed - migration is cheaper than when you last priced it.** Much of a migration is mechanical: translating patterns, writing tests that were never written, documenting what nobody documented. We use AI tools to scan large codebases quickly, find outdated code, and summarise business logic. If you shelved this in 2023 because of the quote, the quote has changed. - **The board question - "What's our AI plan?" has an honest answer.** For most established companies it isn't a model or a vendor. It's that the core system can't support one: no API surface to connect to, no test coverage to make changes safe, no documentation for an agent to read. Migration isn't a detour from your AI strategy; for many businesses it *is* the first phase of it. - **The new risk - agents on an unguarded codebase are a liability.** The fastest way to ship a serious incident in 2026 is to let AI tools loose on a system with no tests, no review gates, and no reliable way to roll back. Teams under pressure to "use AI" are doing exactly that. Migrating puts the guardrails in before the pressure does the damage. The cheapest AI strategy most established businesses can buy is a codebase their tools can actually read. ## A safer way to modernize your platform We use incremental migration strategies that keep your system running while improving it step by step. Full rewrites are the reason this work has a bad reputation: they take years, deliver nothing until the end, and fail in public. - No risky full rewrites - Improvements delivered early, not years later - Your system keeps running throughout the transition - Your existing business logic is preserved - Risk reduced at every step, not deferred to the end 1. **Audit.** We identify the risks, bottlenecks, and hidden costs in what you're running and put a number on them. 2. **Roadmap.** A prioritised modernization plan. Our consultants work alongside your developers to map the real scope of your business logic. 3. **Migration.** We upgrade your system in phases, without downtime. First results in 4–6 weeks. 4. **Optimization.** Performance, maintainability and future flexibility, plus the tests and documentation that make AI tooling productive on it. ## What changes, in the terms your board cares about **Before migration:** 12-year-old platform, fragile codebase, changes feared, monolithic architecture, unresolved security concerns, performance bottlenecks, high dependency on one developer. **After migration:** stable, expandable codebase, modular architecture, no downtime during transition, faster releases, safer deployments, knowledge documented, not held by one person. - **Faster feature delivery** - modern tooling and a streamlined architecture reduce friction, so teams ship quicker and iterate with confidence. - **Lower maintenance costs** - cleaner code and current dependencies cut technical debt and the time spent on fixes and upkeep. - **Better stability** - modern frameworks, testing practices, and predictable deployments mean fewer production incidents. - **Reduced security risk** - up-to-date libraries and current practice eliminate known vulnerabilities and strengthen your posture. ## Your concerns, and what we actually say to them These are the three objections we hear on nearly every first call. We'd rather answer them here than pretend they don't come up. **"It still works. Why change?"** You're not choosing between change and stability. You're choosing when the change happens and who controls it. Migrate now and you get a platform worth building on for the next ten to twenty years. Old architectures don't cut it any more, and the gap widens every quarter. **"Migration sounds risky."** It is, done the usual way. Our strategies minimise risk and downtime precisely because we don't do full reconstructions: you get results from incremental rewrites, in phases, with the system live throughout. Each phase leaves you in a working, deployable state. **"There's no time for this."** There rarely is, until there suddenly is: a failed audit, a lost deal, a resignation. Making time before that point is the cheapest version of this decision. And because your team keeps shipping throughout, it costs less of their time than you're assuming. ## The commercial terms are the reassurance Migration projects have a reputation for overrunning. We structure engagements so the worst case is a small, contained loss, not a stalled programme. - **Exit - stop between any phase.** Fixed price, defined deliverable, phase by phase. Stop after phase one if you want to, and keep everything delivered so far. - **Ownership - you own everything.** Code, documentation, and infrastructure are yours from day one, in your repositories and your accounts. No proprietary layer you keep paying us for. - **Continuity - your roadmap keeps moving.** Your team continues shipping to customers throughout. We don't ask businesses to pause product development for six months, because most of them can't. - **Delivery economics - we use AI agents, and you see the benefit.** Our engineers work with Claude Code and equivalent tooling under human review. That shows up in your fixed price and your timeline, not quietly in our margin. - **Accountability - named people, not a pool.** You know who is on your project and you talk to them directly. Team changes are agreed with you, not announced to you. - **Handover - built to be left.** Every engagement ends with documentation and working sessions so your team can carry it, including how to run agent tooling safely on it. ## Twenty years of not being the cheapest option Two decades in the PHP ecosystem, and the credentials to go with it. - Maintainers of Dotkernel, now v7 - Mezzio and Laminas components - PHP since 2005 - Zend Certified Engineers - Official Laminas commercial vendor ## Platform migration: frequently asked questions ### Surely AI alone can do the migration. Why do I need your help? AI tools are genuinely pivotal in modernising legacy PHP, and we use them daily - to scan large codebases quickly, find outdated code, and summarise business logic. What they don't do is make the final decision. A fifteen-year-old codebase has business rules in it that nobody wrote down and no tool can infer. An experienced engineer is better at reviewing changes, understanding technical context, and making sure an update is safe for production. AI changed the cost and the timeline, not the need for judgement - and the projects we get called in to rescue are usually the ones that skipped that part. ### How much does a PHP migration cost? It depends on the size and complexity of the application, and anyone who quotes you before seeing the code is guessing. The first step is a fixed-fee audit of your codebase; from those results we can estimate the migration properly. What we will say up front: these programmes cost meaningfully less to deliver than they did three years ago. If you priced this in 2022 or 2023 and shelved it, that number is out of date. ### How long does it take? Simple applications can be migrated in weeks; more complex codebases take months. We favour progressive migration because full rewrites are riskier, but we don't rule anything out - the choice is made on the project's details, not on principle. In either case you should expect the first visible results in four to six weeks. ### Do we have to stop building new features? No. That's the single most common reason these projects never start, so we designed around it. Your team keeps shipping on the current system while the new one is built beside it and takes over gradually. ### I have developers of my own. Why work with Apidemia? Rarely because your team can't - usually because they're already fully committed to keeping the current system running, and this work competes directly with that. We're often brought in so the internal team doesn't have to choose. The other reason is pattern recognition. Our engineers have worked with PHP for decades. They built on the architectures that later became difficult to work with, then migrated away from them. They know the downsides of the old ways and the strengths of the new ones because they've lived on both sides. ### Why should I update my PHP at all? Legacy applications get harder to maintain, less secure, and less efficient every year, and the cost shows up as slower delivery and harder hiring long before it shows up as an incident. A modern architecture improves code quality and performance, and current PHP frameworks have proven to be a better foundation to build on. We've written about this at length - see [why up-to-date PHP versions matter](https://www.dotkernel.com/best-practice/zf-is-retired-laminas-mvc-is-retiring-consider-it-solved/). ### What if we want to stop halfway? You can, at the end of any phase. Each phase leaves the system in a working, deployable state, never half-migrated. You keep the code and the documentation regardless. ## Start with a Legacy System Health & Migration Audit A fixed fee, a few days' work, and a written answer instead of an open-ended worry. No guesswork, no vague advice, and no obligation to do the migration with us. - A full risk assessment - Hidden cost analysis - A clear migration roadmap - An AI-readiness review - Recommendations tailored to your system ## Start with a conversation, not a proposal We're currently open for business. Thirty minutes, no obligation, no slides. If we're not the right fit we'll say so and point you somewhere better. 1. **You send a few lines.** What the system does and what's prompting the question now. 2. **We reply within one working day.** A first read and two or three questions. 3. **A 30-minute call.** With the people who'd actually do the work. 4. **A written recommendation.** Options, rough cost, and what we'd do first.