One job, clearly done
Each resource stays focused on one planning problem, so teams can adopt it without a new service or integration.
CMS migration planning
Plan the Drupal 7 migration before the import run.
One workbook for the decisions that otherwise get lost across tickets, exports, and spreadsheets: content inventory, field mappings, modules, redirects, and release QA.
Get the workbook — $29
Built for real projects
Documentation and source notes ship alongside the product, with clear limits on what it does not automate.
No site access required
Our first release is a local workbook. It does not connect to a CMS, collect site data, or modify a production environment.
First release
Drupal 7 to Drupal 11 Migration Workbook
A structured Excel workbook for the planning work around a Drupal 7 migration. Start by setting the project brief, then use its connected working tabs to turn open decisions into a visible migration plan.
- Content inventory, field map, module plan, redirect map, and migration QA register.
- Formula-driven overview, reusable tables, dropdowns, and no macros or site connection.
- One-time purchase: USD 29.
See all seven tabs, column by column, before you buy — screenshots of the file itself, the licence, and the refund terms.
What is inside
A working record for the decisions that block migration.
- Set the project brief. Record the migration owner, source and destination environments, target date, and approach.
- Build an inventory. Track pages, nodes, media, users, terms, menus, and other entities before technical work starts.
- Make mapping decisions visible. Document direct fields, transformations, defaults, unresolved questions, and the people responsible.
- Plan modules and redirects. Record replacements, rebuilds, removals, dependencies, legacy URLs, and staging validation.
- Run release QA. Track acceptance criteria, blockers, ownership, and status through launch readiness.
Free to read
Start with the kickoff checklist
Before deciding whether the workbook is worth $29, read the free checklist it is built around: the ten decisions that stall a Drupal 7 migration, each with a test for telling when it is genuinely settled. No signup, no email required.
Free tool
Find out what you are actually carrying
Before any of the ten decisions can be made, somebody has to know what is in the codebase. Our free inventory scanner reads a Drupal 7 site and reports the custom code that no longer exists in Drupal 10, the custom fields and entities with no obvious destination, and the real Drupal 10/11 release status of every contributed module — measured from drupal.org, not guessed. One file, no dependencies, MIT licensed.
Paid product · USD 39
Turn that scan into the document that gets the work approved
The scanner says what is in the codebase. The workbook tracks the decisions once the project is approved. The Drupal 7 Migration Scope Builder is the step in between: three commands turn the scanner's own --json output into a client-ready scope — phases, work packages with the scan evidence behind each one, a contributed-module decision sheet, a risk register, and an estimate calculated from your hours and rates. It ships no default hours, and refuses to estimate until you supply them.
See what it writes, and what it will not do — the commands, the five output files, the licence and the refund terms.
Purchase terms
Clear scope, simple terms
One purchase permits an organization to copy and adapt the workbook for its own internal client work. Do not resell, redistribute, or publish it as a standalone template.
It is a planning tool, not a migration engine, consulting service, backup, security review, or substitute for staging and automated tests. It does not connect to or modify a Drupal site.
Request a refund within 14 days of purchase by emailing hello@practicalmodules.com.
Contact
Questions about the workbook?
Email hello@practicalmodules.com. The workbook is self-serve and does not include consulting.