| Custom plugin | Upgrade and refactor | Move to Laravel |
|---|
| When | A working site is missing one specific feature. | The site does its job, but its code or PHP version is a liability. | The system has grown into an application with its own business rules. |
|---|
| What you keep | Everything: the site, the content and how you edit it. | The content, the URLs and nearly all of the structure. | The data and the rules; the code gets rewritten module by module. |
|---|
| Risk | Low, as long as the plugin is independent of the theme. | Moderate: needs a staging copy and page-by-page checks. | High, reduced by migrating in pieces with tests. |
|---|
| Upkeep afterward | Update the plugin alongside WordPress. | Keep pace with PHP, WordPress and plugin release cycles. | One major Laravel release a year, plus automated tests. |
|---|
Custom plugin
- When
- A working site is missing one specific feature.
- What you keep
- Everything: the site, the content and how you edit it.
- Risk
- Low, as long as the plugin is independent of the theme.
- Upkeep afterward
- Update the plugin alongside WordPress.
Upgrade and refactor
- When
- The site does its job, but its code or PHP version is a liability.
- What you keep
- The content, the URLs and nearly all of the structure.
- Risk
- Moderate: needs a staging copy and page-by-page checks.
- Upkeep afterward
- Keep pace with PHP, WordPress and plugin release cycles.
Move to Laravel
- When
- The system has grown into an application with its own business rules.
- What you keep
- The data and the rules; the code gets rewritten module by module.
- Risk
- High, reduced by migrating in pieces with tests.
- Upkeep afterward
- One major Laravel release a year, plus automated tests.
As of October 2026, each PHP version gets two years of active support and two more of security-only fixes. PHP 8.1 and older no longer receive patches.