Coming soon

A studio is on its way.

I am growing my Webflow practice into QDS, a design and development studio. The new site launches soon. Until then, write to me.

[email protected]

Trusted by

Use cases

When this fits

You need layouts the template does not allow.

The team bends content to fit fixed sections.

In Webflow

Pages built from your own components, in the order you need.

Your team needs a real CMS.

Content that should be structured lives in plain pages.

In Webflow

CMS collections for case studies, team, jobs or anything you publish often.

New pages take too long to launch.

Each campaign page has to be set up and adjusted by hand.

In Webflow

New pages from sections that already exist, so a launch needs no new template.

What moves, what changes

Each part of your Squarespace site has a place in Webflow. We map them before the build, so nothing is left behind.

In Squarespace

In Webflow

Pages

Pages built from a component library

Blog posts

A CMS collection your team edits

Collections (events, portfolio)

CMS collections, one per type

Categories and tags

Reference fields, for filters and lists

Template and site styles

A design system, set once for every page

Extensions and code blocks

Native Webflow features, or an integration where needed

URLs

Kept where possible, redirected where not

SEO titles and descriptions

Page settings and CMS fields, carried over or corrected

Media library

Webflow assets, resized and compressed

Forms

Webflow forms, connected to your tools

What you get

An inventory of pages, content, extensions and forms, with what moves and what is retired.

The site rebuilt in Webflow, with the current design or a new one.

Blog posts and collections imported into CMS collections.

Redirects for every old address that changes.

Titles, descriptions and schema carried over or corrected.

A check in Google Search Console after launch.

Included in every project

A design system.

Colors, type and spacing are set once.

A component library.

New pages from sections that already exist.

Structure for search and AI.

Headings, titles and schema at launch.

A handover.

A walkthrough and a guide to editing.

How it works

Step 01

Call.

We look at your Squarespace site together and talk about what you want to change.

Step 02

Inventory and proposal.

We list pages, content, extensions and forms, and send the scope and price.

Step 03

Build and import.

We build the site in Webflow and import your content into the CMS.

Step 04

Redirects and testing.

We map every old address and test the site on a staging link.

Step 05

Launch.

We switch the domain and check that old links land on the right page.

Step 06

Check after launch.

We review Google Search Console and fix what it reports.

FAQ

Questions

01
Can you move our content automatically?

Blog posts, yes: Squarespace exports them in a file we import into the Webflow CMS. Other pages are rebuilt, because their layout does not export.

02
What happens to our extensions and code blocks?

We check what each one does. Most become Webflow features or integrations. Custom code is moved where it is still needed.

03
Will our URLs change?

We keep addresses where possible. Where they change, we set up redirects so old links keep working.

04
Can we keep our current design?

Yes. We can rebuild the current design in Webflow, or design a new one as part of the move.

05
How does our team edit content after the move?

In Webflow, on the page or in the CMS. You get a walkthrough and a guide at launch.

06
Who owns the site after the move?

You do. The site lives in your Webflow account.

Tell us about your Squarespace site.