A rebuild of a Drupal site, an open-source system for managing website content, takes no fixed amount of time. A small brochure-style site moves quickly, while a large membership, commerce, or multilingual site takes much longer.
From scratch means a fresh codebase, fresh content structure, fresh design, and fresh settings. Old text and files may carry over, but the old build does not. That clean break makes scope the main driver of time.
Table of Contents
- What does "from scratch" include?
- What changes the timeline most?
- How should you plan content and data?
- How can you keep the rebuild on schedule?
What does "from scratch" include?
A fresh rebuild starts with planning and content modeling. Content modeling means deciding what kinds of pages and fields the site will use. The team then builds those structures, user roles, and permissions in a clean install.
Design and front-end work come next. Theme means the templates, styles, and scripts that control how pages look and act. Editors then enter or import content, test forms and access, and prepare launch checks.
What changes the timeline most?
Scope decisions add work in clear ways. Custom layouts, workflows, and connections to other systems each need build and test time.
Review rounds also shape time. Each round of feedback needs changes and fresh checks. Fewer decision-makers and clear approvals keep that loop short.
- Number of content types, page layouts, and user roles
- Amount of old content that needs cleaning and mapping
- Number of forms, search tools, and system connections
- Need for new design, accessibility checks, and language versions
How should you plan content and data?
Start with a content audit before building. List what to keep, merge, archive, or rewrite. A smaller, cleaner set cuts modeling, design, and entry work.
Treat migration as its own task. Migration means moving text, images, files, and user accounts into the new structure. Test with real examples early, because messy links, files, and permissions cause rework later.
How can you keep the rebuild on schedule?
Lock scope in writing before building starts. List required pages, features, and connections, plus what will wait for later. A shared list helps the team say no to late additions.
Build in small releases and test with real editors. Fix content entry, logins, and forms before polishing design details. Hold new requests for a later phase once final testing starts.
