https://webpro.company/blog/tag/migration/ Drupal version upgrades and migrations — moving from older to newer versions without losing data or disrupting operations. en-US Sat, 20 Jun 2026 06:00:00 GMT https://webpro.company/blog/drupal-7-migration-statistics-2026 https://webpro.company/blog/drupal-7-migration-statistics-2026 Sat, 20 Jun 2026 06:00:00 GMT Migration Drupal Audit Security A Drupal 7 migration in 2026 should not be treated as a simple technical upgrade. The statistics point to a wider operational risk that requires audit work, budgeting, content migration planning, and editorial interface decisions. Drupal 7 Has Not Disappeared, Even Though Official Support Has Ended Official security and compatibility support for Drupal 7 ended on 5 January 2025. Drupal.org explains on its Drupal 7 End of Life page that Drupal 7 no longer receives regular community security or compatibility updates after that date. In 2026, the question is no longer whether Drupal 7 will reach end of life. It already has. Public usage data still shows that many websites have not yet moved to a newer Drupal version or another platform. According to Drupal.org usage statistics, more than… https://webpro.company/blog/drupal-cms-1-to-2-upgrade https://webpro.company/blog/drupal-cms-1-to-2-upgrade Thu, 18 Jun 2026 06:00:00 GMT Migration Drupal Maintenance Drupal CMS 2.0 brings a new starting point, Canvas and site templates, but an existing site created from Drupal CMS 1 does not automatically become the same thing. Before changing it, you need to understand what the site actually uses. Drupal CMS 2.0 raises an obvious question: if a site started from Drupal CMS 1, can it simply be upgraded to Drupal CMS 2? The short answer: carefully. Drupal CMS is not a product version in the same sense as a Drupal Core major version. The Drupal CMS project page describes it as a starting point for new sites. Once a site has been created, what you have is a Drupal site with selected modules, configuration and content. That means Drupal CMS 1 to 2 should not be treated as just a Composer command. It should be treated as a technical change to an… https://webpro.company/blog/ai-in-drupal-migration-planning https://webpro.company/blog/ai-in-drupal-migration-planning Tue, 05 May 2026 06:00:00 GMT AI Migration Drupal Drupal migration includes a lot of repeated analysis: modules, fields, custom code, logs and test scenarios. AI can help when it is used with guidance. Where AI helps AI tools, including OpenAI, can help process a large amount of information faster. They do not replace code access or developer judgement, but they help create the first structure. AI can help with: summarising custom code patterns; finding risks in a module list; drafting test scenarios; grouping migration tasks; preparing documentation drafts. Where AI should not be trusted alone AI does not automatically know which workflow is business-critical or which data loss is unacceptable. It can also suggest outdated Drupal APIs or overly generic solutions. WebPro uses AI as an assistant in AI-assisted Drupal work, but final… https://webpro.company/blog/drupal-11-migration https://webpro.company/blog/drupal-11-migration Sat, 02 May 2026 06:00:00 GMT Drupal Migration The first task in a Drupal migration is usually not writing code. The first task is understanding what exists and what the business depends on. What to assess first which modules are critical and whether they have an upgrade path; which content types, fields and views are actually used; which API connections or manual workflows depend on older logic; which design or accessibility issues should be fixed at the same time; which automated tests must exist before the move. Good migration reduces surprises When risks are mapped first, the work can be split into smaller steps. This makes scope easier to estimate, keeps the public website stable and avoids turning the migration into uncontrolled rebuilding. The WebPro Drupal scanner gives a first view of the site's current state based on… https://webpro.company/blog/drupal-migration-upgrade-or-maintenance https://webpro.company/blog/drupal-migration-upgrade-or-maintenance Sat, 07 Mar 2026 06:00:00 GMT Drupal Migration Maintenance Many Drupal site owners know something needs to be done — but not exactly what. Maintenance, upgrade and migration solve different problems and cost differently. Three main situations come up in the lifecycle of a Drupal site, each requiring a different kind of technical response. Choosing the wrong service does not fix the problem — it delays it. Maintenance Maintenance suits a site running on Drupal 9, 10 or 11 that is fundamentally healthy but needs ongoing technical attention. Maintenance covers: applying security updates to Drupal core and modules; keeping PHP, server and dependencies current; managing performance, backups and certificates; fixing small bugs and making content changes; monitoring and responding to issues. Maintenance is not a one-time job — it is an ongoing… https://webpro.company/blog/custom-module-audit-before-drupal-migration https://webpro.company/blog/custom-module-audit-before-drupal-migration Tue, 03 Mar 2026 06:00:00 GMT Audit Migration Drupal Drupal core has a documented upgrade path. The real project risk often lives in custom modules that have become critical to the business over the years. What to look for in custom code Drupal update documentation describes the general path, but custom modules must be reviewed project by project. An audit should check: whether the module uses deprecated APIs; which hooks and services are critical; whether the data model is documented; whether the module depends on an old contrib module; whether the feature can be replaced by standard Drupal functionality. How this helps estimation When the state of custom code is known, migration becomes a set of decisions: what to port, what to rewrite and what is no longer needed. This reduces the chance that developers discover major risk in the… https://webpro.company/blog/drupal-upgrade-cost https://webpro.company/blog/drupal-upgrade-cost Tue, 13 Jan 2026 06:00:00 GMT Migration Drupal The same Drupal version upgrade can be a small maintenance task on one site and a full migration on another. The difference comes from content, modules and business logic. What affects the price Updating Drupal depends on how much of the site follows standard Drupal patterns and how much is custom-built. The version number alone is not enough for estimating the work. Typical cost drivers are: contrib module status and compatibility; custom modules and custom themes; the number of content types, fields and views; external APIs, payments, CRM or ERP integrations; test environment, automated tests and release planning. Why a cheap quote can become expensive If risks are not assessed, they appear in the middle of the project. The upgrade then becomes a chain of urgent fixes and the final… https://webpro.company/blog/drupal-10-end-of-life-and-drupal-11-readiness https://webpro.company/blog/drupal-10-end-of-life-and-drupal-11-readiness Fri, 09 Jan 2026 06:00:00 GMT Migration Drupal A Drupal 10 site does not break overnight. The risk appears when the upgrade plan is left too late and dependencies are not ready. Why this already matters Drupal.org publishes the official Drupal core release schedule. According to that schedule, Drupal 10 reaches end of life on December 9, 2026. This does not mean every Drupal 10 site must be rebuilt immediately. It means site owners should know whether their site is ready for Drupal 11 before the deadline becomes close. A weak plan is to wait until support has ended. A better plan is to check: which Drupal 10 minor version is running; whether PHP and the database match Drupal 11 requirements; whether contributed modules support Drupal 11; whether custom code uses deprecated APIs; whether the upgrade can be tested without touching… https://webpro.company/blog/drupal-7-in-2026-what-to-do https://webpro.company/blog/drupal-7-in-2026-what-to-do Tue, 06 Jan 2026 06:00:00 GMT Migration Drupal Security A Drupal 7 website can still look fine in 2026, but official security support has ended and every new change is becoming harder to control. Why this is no longer a normal update Drupal 7's official lifecycle has ended. That means an old site does not only need module updates. It needs a decision: continue with known risk, buy temporary support or move to a newer platform. Module updates have stopped. If a new security vulnerability is found in a Drupal 7 module, no automatic fix will arrive — someone must patch it manually or accept the risk. What the real risks are Most Drupal 7 sites are still running without any visible problem. The risk does not appear immediately — it grows over time: Security vulnerabilities — newly found weaknesses in modules are no longer patched automatically.… https://webpro.company/blog/drupal-migrate-api https://webpro.company/blog/drupal-migrate-api Thu, 24 Oct 2024 06:00:00 GMT Migration Drupal Development Content migration is part of every significant Drupal project. Migrate API is the right tool for the job — here is how it works and what to plan for. What Migrate API is Drupal Migrate API is a core framework for importing content from different sources in a structured way. It has three parts: Source — where data comes from (old Drupal database, CSV, JSON, XML, REST API, Excel file, etc.). Process — how data is transformed (renaming fields, converting values, filtering, resolving references). Destination — where data goes (Drupal node, taxonomy term, media entity, user, etc.). Common migration scenarios Drupal 7 → Drupal 11 The most common migration. Drupal provides official migration modules (, ) that understand Drupal 7's data structure. These migrate automatically: Content types and…