WordPress’s extended upgrade instructions require a usable backup of the database and every file before a manual upgrade, and suggest upgrading incrementally when crossing more than two major releases. Treat a neglected site as a staged recovery project.
\nThe WordPress extended upgrade instructions start a manual upgrade by backing up the database and all WordPress files, including .htaccess, and verifying that the backups exist and are usable, which the page calls essential. Plugins are deactivated before the upgrade, and the page says not to attempt it until those first four steps are complete. During file replacement, wp-config.php, the wp-content folder, a customized .htaccess and a site-root robots.txt are kept.
\nWordPress says one-click updates work on most servers, and that problems are probably related to filesystem permissions. Upgrading directly across many versions is supported with proper backups, but when crossing more than two major releases the page suggests considering an incremental upgrade to avoid conflicts and reduce the risk of database damage. For very old releases it describes expected losses of some theme and plugin functionality, though not of content.
\nUse this for inherited or long-unpatched WordPress sites and for planning repair work on them. Sites already on current releases with working automatic updates need ordinary update monitoring rather than this procedure.
\nDSE recommends treating an upgrade of a neglected WordPress site as a staged project with a tested restore point at each step. Copy the site to a staging host, take and test-restore a full database and file backup, record the theme and plugin versions, plan any intermediate WordPress releases needed, and only then upgrade core, PHP, themes and plugins in a controlled order before repeating the process on production.
\nAfter each stage, sign in, publish and preview a test post, exercise forms and any e-commerce checkout, check the PHP error log, and confirm the dashboard reports the expected WordPress version. Keep the backup from each stage until the site has run cleanly in production.
\nWordPress Developer Resources — Upgrading WordPress: Extended Instructions. Reviewed October 18, 2026.
", "content_text": "WordPress’s extended upgrade instructions require a usable backup of the database and every file before a manual upgrade, and suggest upgrading incrementally when crossing more than two major releases. Treat a neglected site as a staged recovery project.\nSource facts\nThe WordPress extended upgrade instructions start a manual upgrade by backing up the database and all WordPress files, including .htaccess, and verifying that the backups exist and are usable, which the page calls essential. Plugins are deactivated before the upgrade, and the page says not to attempt it until those first four steps are complete. During file replacement, wp-config.php, the wp-content folder, a customized .htaccess and a site-root robots.txt are kept.\nWordPress says one-click updates work on most servers, and that problems are probably related to filesystem permissions. Upgrading directly across many versions is supported with proper backups, but when crossing more than two major releases the page suggests considering an incremental upgrade to avoid conflicts and reduce the risk of database damage. For very old releases it describes expected losses of some theme and plugin functionality, though not of content.\nApplicability\nUse this for inherited or long-unpatched WordPress sites and for planning repair work on them. Sites already on current releases with working automatic updates need ordinary update monitoring rather than this procedure.\nDSE recommendation\nDSE recommends treating an upgrade of a neglected WordPress site as a staged project with a tested restore point at each step. Copy the site to a staging host, take and test-restore a full database and file backup, record the theme and plugin versions, plan any intermediate WordPress releases needed, and only then upgrade core, PHP, themes and plugins in a controlled order before repeating the process on production.\nVerification\nAfter each stage, sign in, publish and preview a test post, exercise forms and any e-commerce checkout, check the PHP error log, and confirm the dashboard reports the expected WordPress version. Keep the backup from each stage until the site has run cleanly in production.\nOfficial reference\nWordPress Developer Resources — Upgrading WordPress: Extended Instructions. Reviewed October 18, 2026.", "content_markdown": "WordPress’s extended upgrade instructions require a usable backup of the database and every file before a manual upgrade, and suggest upgrading incrementally when crossing more than two major releases. Treat a neglected site as a staged recovery project.\n\n## Source facts\n\nThe [WordPress extended upgrade instructions](https://developer.wordpress.org/advanced-administration/upgrade/upgrading/) start a manual upgrade by backing up the database and all WordPress files, including .htaccess, and verifying that the backups exist and are usable, which the page calls essential. Plugins are deactivated before the upgrade, and the page says not to attempt it until those first four steps are complete. During file replacement, wp-config.php, the wp-content folder, a customized .htaccess and a site-root robots.txt are kept.\n\nWordPress says one-click updates work on most servers, and that problems are probably related to filesystem permissions. Upgrading directly across many versions is supported with proper backups, but when crossing more than two major releases the page suggests considering an incremental upgrade to avoid conflicts and reduce the risk of database damage. For very old releases it describes expected losses of some theme and plugin functionality, though not of content.\n\n## Applicability\n\nUse this for inherited or long-unpatched WordPress sites and for planning repair work on them. Sites already on current releases with working automatic updates need ordinary update monitoring rather than this procedure.\n\n## DSE recommendation\n\nDSE recommends treating an upgrade of a neglected WordPress site as a staged project with a tested restore point at each step. Copy the site to a staging host, take and test-restore a full database and file backup, record the theme and plugin versions, plan any intermediate WordPress releases needed, and only then upgrade core, PHP, themes and plugins in a controlled order before repeating the process on production.\n\n## Verification\n\nAfter each stage, sign in, publish and preview a test post, exercise forms and any e-commerce checkout, check the PHP error log, and confirm the dashboard reports the expected WordPress version. Keep the backup from each stage until the site has run cleanly in production.\n\n## Official reference\n\n[WordPress Developer Resources — Upgrading WordPress: Extended Instructions](https://developer.wordpress.org/advanced-administration/upgrade/upgrading/). Reviewed October 18, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/wordpress-neglected-site-upgrade-verified-backup-incremental/", "url": "https://update.dsesecurity.com/updates/wordpress-neglected-site-upgrade-verified-backup-incremental/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-18" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/wordpress-neglected-site-upgrade-verified-backup-incremental/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Upgrade a neglected WordPress site in planned steps: verified backups first, then incremental releases", "item": "https://update.dsesecurity.com/updates/wordpress-neglected-site-upgrade-verified-backup-incremental/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/wordpress-neglected-site-upgrade-verified-backup-incremental/#article", "identifier": "https://update.dsesecurity.com/updates/wordpress-neglected-site-upgrade-verified-backup-incremental/", "url": "https://update.dsesecurity.com/updates/wordpress-neglected-site-upgrade-verified-backup-incremental/", "headline": "Upgrade a neglected WordPress site in planned steps: verified backups first, then incremental releases", "description": "WordPress’s extended upgrade instructions require a usable backup of the database and every file before a manual upgrade, and suggest upgrading…", "abstract": "WordPress’s extended upgrade instructions require a usable backup of the database and every file before a manual upgrade, and suggest upgrading incrementally when crossing more than two major releases. Treat a neglected site as a staged recovery project.", "articleBody": "WordPress’s extended upgrade instructions require a usable backup of the database and every file before a manual upgrade, and suggest upgrading incrementally when crossing more than two major releases. Treat a neglected site as a staged recovery project.\nSource facts\nThe WordPress extended upgrade instructions start a manual upgrade by backing up the database and all WordPress files, including .htaccess, and verifying that the backups exist and are usable, which the page calls essential. Plugins are deactivated before the upgrade, and the page says not to attempt it until those first four steps are complete. During file replacement, wp-config.php, the wp-content folder, a customized .htaccess and a site-root robots.txt are kept.\nWordPress says one-click updates work on most servers, and that problems are probably related to filesystem permissions. Upgrading directly across many versions is supported with proper backups, but when crossing more than two major releases the page suggests considering an incremental upgrade to avoid conflicts and reduce the risk of database damage. For very old releases it describes expected losses of some theme and plugin functionality, though not of content.\nApplicability\nUse this for inherited or long-unpatched WordPress sites and for planning repair work on them. Sites already on current releases with working automatic updates need ordinary update monitoring rather than this procedure.\nDSE recommendation\nDSE recommends treating an upgrade of a neglected WordPress site as a staged project with a tested restore point at each step. Copy the site to a staging host, take and test-restore a full database and file backup, record the theme and plugin versions, plan any intermediate WordPress releases needed, and only then upgrade core, PHP, themes and plugins in a controlled order before repeating the process on production.\nVerification\nAfter each stage, sign in, publish and preview a test post, exercise forms and any e-commerce checkout, check the PHP error log, and confirm the dashboard reports the expected WordPress version. Keep the backup from each stage until the site has run cleanly in production.\nOfficial reference\nWordPress Developer Resources — Upgrading WordPress: Extended Instructions. Reviewed October 18, 2026.", "datePublished": "2026-10-18T21:00:19+00:00", "dateModified": "2026-10-18T22:22:06+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/wordpress-neglected-site-upgrade-verified-backup-incremental/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/wordpress-neglected-site-upgrade-verified-backup-incremental/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Upgrade a neglected WordPress site in planned steps: verified backups first, then incremental releases" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Playbook", "Information priority" ], "genre": "Playbook", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 345, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "WordPress Developer Resources — Upgrading WordPress: Extended Instructions", "url": "https://developer.wordpress.org/advanced-administration/upgrade/upgrading/" } } ] } }