Practical guide
Plan a legacy Drupal theme migration
Inventory content, dependencies, and URLs before rebuilding a Drupal 6 or 7 design on a supported platform.
Content updated
Separate the design from the old package
A familiar layout can remain useful as a design reference even when its original software dependencies need replacement. Inventory the existing content, features, files, and URLs before deciding how to rebuild.
Understand the support status
Drupal 6 reached end of community support on February 24, 2016. Drupal 7 reached end of life on January 5, 2025. Compatibility statements on the Antsin theme pages describe the historical packages.
Sources: Drupal 6 end-of-life notice and Drupal 7 security advisory. Consult Drupal’s release schedule when selecting a supported target.
Build a migration inventory
- Export page URLs, titles, main content, image files, and downloadable documents.
- List content types and fields. Keep identifiers and document revisions attached to the right records.
- Record menu behavior, forms, Views, galleries, commerce, and any third-party integrations.
- Decide which features to rebuild, replace, or retire. Treat Flash and old slideshow dependencies as replacement work.
- Map every old URL to the retained page or a specific replacement. Use server redirects when a URL changes.
Rebuild one complete journey first
Choose a route from the homepage to a useful detail page and then to an inquiry or other next step. Rebuild that whole route, including navigation, error states, and confirmation behavior, before migrating every page.
Check the published site
Compare the old and new content inventories, test redirects and downloadable files, inspect page titles and canonical URLs, and verify that missing pages return an actual HTTP 404. Test on a phone and with a keyboard. A custom error design alone does not set the HTTP status.
A migration is more than a core update
Moving a Drupal 6 or 7 site to a modern Drupal generation requires migrating content and configuration into a new site. The old theme must be rebuilt, and contributed modules may need replacement or custom migration work. Keeping a familiar visual direction does not make the original theme package compatible.
Source: Drupal’s migration overview.
Worked example: preserving a small company site
Suppose an old site has a company introduction, twelve service pages, an image gallery, and a quote form. Keep the service page URLs where their purpose remains the same. Rebuild the gallery with captions and image rights recorded. Treat the form as a separate feature with delivery and error-state checks. Compare content counts and attachments before changing the live hostname.
| Old route | Decision | Acceptance check |
|---|---|---|
| /services/finishing | Keep the URL if the service page still exists. | The retained page returns 200 and links to its supporting documents. |
| /node/42 | Redirect to the specific equivalent service page. | A permanent server redirect reaches the final page without a chain. |
| /old-gallery | Redirect only if a relevant replacement gallery exists. | The destination preserves the subject and useful project context. |
| /retired-offer | Use 404 or 410 when no equivalent content remains. | The response is an actual error status, with useful recovery navigation. |
References: Google’s redirect guidance and HTTP status guidance.
Build an acceptance record before switching over
For each important journey, record the starting URL, expected destination, required content, supporting files, and observed result. Check the homepage-to-detail route, contact or quote submission, menu behavior, and a missing URL. Keep a dated backup and a clear route back to the old deployment until the checks pass.
The planning worksheet includes a migration record. Use Drupal’s preparation guide to plan the source-site preparation.