Real files first
Migrate the actual project tree, not editor metadata.
DW Site Migration
Plan a clean Dreamweaver-to-Wappler migration by mapping files, site roots, and the first checks to run after import.
A Dreamweaver migration works best when you migrate the site structure, not the old assumptions
Wappler can work with the real files from an existing site, but it does not depend on hidden Dreamweaver site-definition behavior. The migration mindset is simple: bring the project files over cleanly, identify the actual web root and support folders, then verify everything inside Wappler using the file and page tools.
Clear roots
Know which folder is public, which holds includes, and where assets live.
Progressive upgrade
Stabilize the imported site before adding new Wappler-specific features.
Copy or open the site as a real project folder.
Confirm which files are pages, partials, assets, and server-side includes.
Use Wappler's managers to verify structure before refactoring or modernizing.
The practical migration order is file shape, page shape, then dynamic improvements
Start by confirming the imported file tree, then open representative pages and make sure the folder references still make sense. Only after the static structure is stable should you begin adding routing, data bindings, or new server actions. That order keeps migration bugs separate from modernization work.
TIP: If the original site mixes content, assets, and includes loosely, stabilize the structure first. Wappler becomes much easier once the file layout is predictable.
Use File Manager to confirm the imported folders and filenames.
Use the page and editor tours to verify how the old pages map into Wappler's page workflow.
Modernize in small steps: layout cleanup first, then App Connect or Server Connect features where needed.
Next steps
The quickest way to trust a migrated site is to inspect it through the same managers you’ll use every day after the migration.