What’s included?
- Management, validation, and implementation of upgrades in a standalone testing environment, including:
- Major WordPress versions.
- Major PHP versions.
- Most third-party plugins that are incompatible with newer WordPress or PHP versions. (Exclusions apply).
- Expert debugging and validation.
- A high-level report outlining tested components (WordPress, PHP), included plugins (incompatible or all), and planned code changes.
- Step-by-step deployment guidance, listing all steps for the production upgrade.
- An executive summary that highlights all deliverables after completion.
Available add-ons:
- All 3rd-party plugins with an available update.
- Any of the following plugins:
- WooCommerce.
- Divi/Elementor/Page Builder plugins.
- bbPress.
- MemberPress.
- Event Calendar.
- WP Job Manager.
Is this service for me?
Companies who benefit from this service may:
- Want to prioritize revenue-generating activities like feature development over maintenance work.
- Have specific upgrade deadlines to meet.
- Not have developer resources for performing upgrades.
- Need smooth, reliable upgrade implementations.
- Seek expert-managed upgrades for peace of mind.
- Need application updates as part of a Migration/Launch service.
How does it work?
A typical service is 2-4 weeks for single-sites or small multisites. Timing scales up in the Testing & QA phase. Optional customer QA and coordinating the production upgrade can also extend this timeline.
| Phase | VIP will: | Customer will: |
|---|---|---|
| Week 1 Discovery | Schedule kickoff call. Review Discovery Questionnaire. | Complete Discovery Questionnaire. |
| Week 2 Kickoff | Lead Kickoff call to formalize scope. | Join Kickoff call. |
| Week 2-3 Testing & QA | Confirm access to source site. Review site for roadblocks to migration. | Optional: Validate and test site. Confirm production upgrade date. |
| Week 4 Implementation | Upgrade production site. 48 hours of post-upgrade support if issues are identified. | Optional: Upgrade production site. Validate production site. Report upgrade-related issues within 2 business days (48 hours). |
Frequently Asked Questions
Which third-party plugin upgrades aren’t included in a standard service?
These plugins require additional testing and are available as an add-on.
- WooCommerce.
- bbPress.
- MemberPress.
- Event Calendar.
- WP Job Manager.
- Page builders like Divi, Elementor, Beaver Builder.
Why should I upgrade WordPress, PHP, and plugins?
Upgrading WordPress, PHP, and your plugins helps to ensure your website remains secure, runs smoothly, and stays current with the latest exciting functionality.
- Functionality: Regular updates introduce new features and enhancements that improve user experience and site functionality.
- Security: Outdated versions and plugins can have vulnerabilities that hackers exploit. While WordPress VIP applies core security patches automatically, you must manually update plugins to protect against known threats.
- Performance: New versions include performance enhancements, bug fixes, and optimizations, ensuring your site runs efficiently.
- Compatibility: Plugins and themes are updated frequently for compatibility with the latest WordPress and PHP versions. Failing to update can result in issues and downtime.
How often should I update PHP?
Each PHP release branch is fully supported for two years after its initial stable release, during which bugs and security issues are fixed in regular point releases.
After this period, the branch is supported for an additional year for critical security issues only, with releases made as needed. WordPress VIP will discontinue support once Security Support is inactive.
How involved do we have to be in this Service?
After the kickoff call, you can remain uninvolved until testing is complete and a production upgrade plan is in place. We’ll notify you when the non-production environment is updated and tested, and most customers conduct their own QA at this stage. You can either follow the production upgrade plan yourself or let us manage the final steps. You’ll also be able to track progress in your Project Portal and ask questions as needed.
Am I allowed to add new content after the service has started?
Absolutely! The testing and validation process will all take place in a dedicated non-production environment. No editorial disruptions are needed.
Am I allowed to commit code after the service has started?
You can commit code after service starts, though any new changes won’t be included in testing since it uses a cloned branch. While we understand that development work can’t completely stop, we recommend minimizing deployments to the production branch to limit untested code.
If we deploy code after the service has started, will it get overwritten by the upgrade?
During an upgrade, only updated plugins will be overwritten—all other code changes will remain intact. Please notify us of any plugin-specific patches so we can preserve them. When we need to modify theme code for fixes, we’ll do so carefully to maintain existing functionality. We’ll document all code changes throughout the process.
Do you use one of our existing non-production (child) environments for testing?
No. We create a new, dedicated child environment specifically for this service, unless requested otherwise. This environment will be removed after the production upgrade and does not count against your contracted environment allotment.
Resources
- Download: Example Upgrade QA Summary report
- Download: Example Upgrade Day Plan
- Download: Upgrade Assurance Overview
Get started with VIP Professional Services
Fill out the form to get in touch with our services team