Website migration planner

Any path. Every file in src/pages/ becomes a page at its own path, at any depth, and a rest parameter ([...slug]) builds paths of any depth from a CMS, so every old path can be rebuilt as it is.

build.format. build.format sets how a static page is written: 'directory' (the default) writes /about/ as about/index.html, 'file' writes about.html, and 'preserve' writes each page as its source file is named, so one site can keep both /blog/ and /about.html. Astro pairs trailingSlash 'always' with 'directory' and 'never' with 'file'.

Trailing slash. trailingSlash ('always', 'never' or the default 'ignore') applies to the dev server and to pages rendered on demand. Astro says trailing slashes on prerendered pages are handled by the hosting platform, and its redirects can't send /about/ to /about, so test how your host answers each form.

Files. Files in public/ are copied into the build untouched, so a PDF or an image keeps its old address when it goes in the same folder there.

Extension. Astro writes pages as folders or .html files. An address ending in .php, .asp or another server extension would need an endpoint file of that name, and how a host serves one as a page isn't Astro's to document, so the plan drafts a 301 to the same path without it.

Underscore. Astro skips files and folders whose names start with an underscore and documents no way to serve a path that begins with one: test it, or redirect it.

Capitals. Astro doesn't document whether routes match capital letters or accented characters exactly, and content collections lower-case entry IDs by default. Test an address with capitals or accents on your build before launch.

Query string. A prerendered page never sees the query string, and Astro's redirects can't match one, so /?p=12 would just show the home page. Redirect these at your host, choosing each target by hand.

Redirects. Astro's redirects option sends a 301 when a server or a supported adapter serves the site; a static build without one writes a page with a meta refresh and no status code. On a static site, put the redirects in your host's file (Netlify and Cloudflare read _redirects).

Any path. Folders under app/ define each URL segment at any depth, and catch-all segments ([...slug]) serve paths of any depth from a CMS, so every old path can be rebuilt as it is.

Trailing slash. By default Next.js answers /about/ with a 308 redirect to /about; trailingSlash: true does the reverse. One form is kept for the whole site and Next.js redirects the other itself, so those URLs need no rule of yours.

.html pages. Next.js documents no page at an address ending in .html. A rewrite can map a path to a page, but no example shows .html, so test one, or use the drafted 301 to the same path without it.

Files. Files in public/ are served from the site's root (public/docs/guide.pdf answers at /docs/guide.pdf), so files can keep their old addresses.

Extension. Next.js documents no page at an address ending in .php, .asp or another server extension, so the plan drafts a 301 from each to the same path without it.

Capitals. Next.js says route parameters are case-sensitive only in its Pages Router docs, and documents nothing about accented paths. Test an address with capitals or accents before launch.

Query string. A redirect can match a query string with has (type 'query'), and Next.js passes the rest of the query on, so /?p=12 can have its own rule. The export writes them; choose each target by hand.

Redirects. redirects() in next.config.js runs before pages and files; permanent: true sends a 308, and the export asks for a 301 with statusCode. A static export (output: 'export') doesn't support redirects, so set them at the host.

Redirect limit. Next.js notes a limit of 1,024 redirects on Vercel (Vercel's own docs now say 2,048) and, past 1,000, suggests a redirect map read by Proxy.

Folders. Static pages can sit in folders and nested subfolders, so a page at /services/web-design can keep its path.

Collection URL. Webflow serves every CMS item at its Collection URL followed by its slug (/post/your-blog-post) and documents no way to put items at the site's root or under date folders, so posts at /my-post/ or /2019/05/my-post/ move to a Collection folder with a 301 each.

Nested Collections. A Collection template page can take a parent folder, nested several levels (/resources/blog/post), since April 2023. Webflow's Page URLs article still says only static pages go in folders, so check the setting in your Designer.

Characters. Webflow supports lowercase Latin letters and numbers in page URLs (its examples also use hyphens). It removes special characters such as ! ~ . & and converts other scripts to Latin letters, and it doesn't say what it does with underscores, so test those.

Capitals. Webflow turns capital letters in page slugs into lowercase, so /About-Us becomes /about-us and needs a 301. Webflow doesn't say whether its redirects match capitals exactly, so test one.

Extension. Webflow removes dots from page slugs, so a page can't live at /about.html or /index.php: each needs a 301 to its new path. Webflow's redirect help shows no example from such a path, so test one after import.

Trailing slash. Webflow's paths have no trailing slash in its examples, and it doesn't document whether /about/ answers or redirects to /about. Publish one page and test it; if /about/ doesn't reach the page, add the drafted 301s.

Files. A PDF or an image isn't a page, and Webflow documents no way to keep a file at its old address: upload it, then redirect the old address to the file's new one if it changed.

Query string. Webflow's redirects can match a query string when ?, = and & are escaped with % (/%?p%=12), and the Webflow export writes them that way. Choose each target by hand.

Languages. With Localization, each locale lives in a subdirectory (/es/) you can rename, so a language folder can keep its paths; translated page slugs need a Localize Advanced or Enterprise plan.

Redirects. 301 redirects need a paid plan and live in Site settings → Publishing. Older rules run first, wildcards use (.*) and %1, they don't apply to localized subdirectories, and a redirect can't sit on a path a published page still uses: unpublish or rename that page first.

CSV import. Redirects can be imported from a CSV with two columns, old path then new path, up to 16 MB. An import replaces every redirect already on the site and one invalid row fails the whole file, so export the current list first and merge.

Redirect limit. Webflow sets no hard limit but recommends 1,000 redirects at most; one wildcard rule can cover a whole folder (/old-blog/(.*) → /blog/%1).

Page paths. Framer turns page names into paths you can edit, and folders add path segments (/about/team), so a page can keep a nested path.

CMS page path. A CMS detail page's path is a folder and the item's slug (/blog/:slug), and you can edit it. Framer documents no root path (/:slug), no path with several folders and no second variable such as a year, so test those, or move the items to one folder with a 301 each.

Characters. Framer doesn't document which characters a path can hold; its SEO guide only advises hyphens over underscores. Test addresses with capitals, underscores or accents before launch.

Extension. Framer documents no page at an address ending in .html or .php, and its static files don't take HTML or PHP. Test one, or use the drafted 301 to the same path without the extension.

Trailing slash. Framer's paths have no trailing slash (it tells proxies to strip one), but it doesn't document how its own hosting answers /about/. Publish one page and test it; if /about/ doesn't reach /about, add the drafted 301s.

Files. On Pro and Enterprise plans, static files (PDF, TXT, CSV, JSON, XML, ZIP and a few more) are served at your domain's root and under /.well-known/. Other folders and file types aren't documented: test them, or redirect the old address.

Query string. Framer's redirect help doesn't say whether a redirect can match a query string (/?p=12), so test one before relying on it.

Languages. Each extra locale gets a prefix you set (/es/), and page paths and CMS slugs can be translated per locale, so a language folder can keep its paths.

Page limit. Framer's plans include 30 pages (Basic) or 150 (Pro), and Pro can add more up to 700. Many old pages may fit better as one CMS collection.

Redirects. Redirects live in Site Settings → Hosting → Redirects (not on Basic) and run in the order you set; * matches any path and :1 reuses it. Framer calls them permanent, giving the code as 308 on one page and 301 on others.

CSV import. Framer's Redirect Sync plugin imports a CSV with from and to columns, paths starting with /; a row whose from already exists updates that redirect.

Redirect limit. Framer allows up to 2,500 redirects per project; a wildcard rule (/old-blog/* → /blog/:1) covers a whole folder in one line.