Moves go wrong in small places. We check all six.

Rankings, forms, integrations, tracking, accessibility and the habits of the people who edit the site. Whatever kind of move you are making, these are what we protect while we build the new setup beside the live one.

“Launches that should take a week take three”

“Our website builder is blocking the business”

“We're worried a move will lose search traffic”

“We don't know which platform to move to”

What gets lost in a move, and what we do about it.

Most of it is not dramatic. It is small things nobody checked, found by customers first.

Search rankings

Old addresses that return an error stop earning traffic, and the pages that took years to rank go with them.

How we prevent it

A redirect map sends every old URL somewhere sensible, so rankings follow you to the new site.

Forms

A form that looks fine on the new site but no longer reaches anyone.

How we prevent it

Every form is tested end to end, through to the inbox or system it feeds, before the switch.

Integrations and data

A connection to your CRM, payments or email tool that nobody remembered was there.

How we prevent it

We list what your site talks to during discovery, then test each connection in staging.

Tracking

Analytics that restart from zero or quietly stop recording conversions.

How we prevent it

Tracking is set up before launch, so you can compare before and after.

Accessibility

A new theme that looks better and works worse with a keyboard or a screen reader.

How we prevent it

Keyboard and screen reader testing against WCAG 2.2 AA, not only an automated scan.

Your editors' habits

The people who update the site every week can't find anything.

How we prevent it

The non-obvious parts are written down, and your team is trained just before launch.

Four ways we can help you with your move

  • 1 of 4

    Switch site platforms

    WordPress, Squarespace, Wix or old Drupal to the platform that fits.

    Old CMS to new CMS
  • 2 of 4

    Rebuild on your same platform

    The same look and pages on a current platform. Rootless moved to Shopify 2.0 this way.

    Shopify theme to Shopify 2.0
  • 3 of 4

    Move a business system

    A CRM, donor or enrollment platform and the site integrations that depend on it.

    Old system to new system, reconnected
  • 4 of 4

    Decide where to move

    A comparison and a straight recommendation before anyone builds.

    Many options to one

Not sure what to do yet? We can help with that.

Knowing you have a problem with your current system or setup doesn't always mean you know where to go or what to do about it. We've seen a lot of solutions in our time and we know the right questions to ask to steer you to the right answer.

The same questions for every option

We don't pick our favorites, because they might not work for your particular needs. Our comparison is fair so you can pick between the winners.

Planned for future growth

We make sure to evaluate not just for today's needs, but also those of your future growth goals so that you don't end up stuck again in a few years.

A straight answer

Buy, connect, or build, with the reasons written down.

Sample matrix. The platforms, ratings and amounts are placeholders, not a real comparison.
What we ask[Platform A][Platform B][Platform C]
Built for organizations like yours? Fits Partly Gap
Connects to the tools you already run? Fits Fits Partly
Your team can edit it without a developer? Partly Fits Fits
Meets WCAG 2.2 AA? Fits Partly Gap
Cost at today's size [amount] [amount] [amount]
Cost at the size you plan to grow to [amount] [amount] [amount]
Our read[Short reason][Short reason][Short reason]

Two moves, two kinds of risk.

Rootless

A Shopify 2.0 rebuild that ran beside the live store for four months, then launched on a single morning.

200+
requests completed on their shared board
4 → 1
purchase templates merged into one
Zero
downtime at launch

Malak is excellent and super knowledgeable. We've already learned so much from them about how to optimize our website and how we can better approach web design from a CX and engineering perspective.

Grayce M.Brand & Community Manager, Rootless

Rosie's House

Four disconnected systems replaced by one platform they chose, connected to Salesforce, with no custom build.

4
systems replaced
52
vendors evaluated side-by-side
No
custom build needed

I can't express enough how grateful I am for everything that you have poured into this project. You set us up well for success. Thank you! Thank you! Thank you!

Marvin S.Program & Community Engagement Director, Rosie's House

Four kinds of moves, one careful way to do it.

Hi there!

We've handled all kinds of website moves and migrations, in our time. Taking care of your most sensitive data and business tools is something that we approach with care and pride because we know how much it means to your business.

Whether we're moving you from one platform to another, helping you switch CRMs, or looking to fully replace and upgrade your current theming on your existing site, we're absolutely the people you want on your team. We treat your data and processes as if they're our own.

Let us handle all of the details while you focus on doing what you do best: running your own business and working with your customers. We'll do what we do best: tracking details, connecting data, and teaching you and your team how to use their new tools.

Malak JanusMagnolia Development

P.S. If a replatform or move isn't right for you, I'll let you know. Sometimes a better solution is to fix what you already have ... and we can help with that too! :)

Which move is yours?

Pick the one closest to your situation. Most real projects mix two.

Switch site platforms

WordPress to Shopify, Squarespace or Wix to a CMS you can grow in, an old Drupal site to something current.

What we do
Build the new site on the new platform beside the live one, move the content that exports, and rebuild the layouts by hand.
What moves
Pages and posts, every old URL with a redirect, forms, analytics, and editing access for your team.
The main risk
Search traffic. Every old URL gets sent somewhere sensible, so rankings follow you.

Blog posts usually export. Layouts and most page content get rebuilt by hand.

Weeks 1 to 2

Discovery and access

Conversations with the people who use the site, a look at analytics and code, and access requests started on day one, because they always take longer than expected.

A list of what moves, who holds each login, and the access we need.

Weeks 2 to 4

Structure and patterns

Sitemap, page structure, and designs for the templates the site is built from. We design patterns, not every page, so your team can build the next page without us.

A sitemap and templates your team can build new pages from.

Weeks 4 to 8

Build in cycles

Templates, then content, then integrations. You review on a staging site at the end of every two-week cycle. Content arriving late is the most common reason this stretches.

A staging site you review every two weeks.

Weeks 8 to 10

Test and redirect

Keyboard and screen reader testing, every device, every form end to end, and a redirect map so search traffic follows you to the new site.

A tested site and a redirect map for every old URL.

Launch week

Launch

Early in the week and early in the day, never on a Friday afternoon. Someone watches analytics and error logs afterward, and your team is trained just before.

A trained team and someone watching the logs.

30 days after

Stabilize

Real traffic finds things testing doesn't. Thirty days of fixes are included, then most clients move to a retainer.

Thirty days of fixes, then a choice about what comes next.

What every move includes.

  • 01

    The built site

    On a platform your team can edit, with design files and editing access handed over.

  • 02

    An accessibility pass

    Tested with a keyboard and a screen reader against WCAG 2.2 AA, not only an automated scan.

  • 03

    Forms and integrations tested

    Every form, payment path and connected system tested end to end before the switch.

  • 04

    Analytics configured

    Tracking set up before launch, so you can compare before and after.

  • 05

    A redirect map

    Every old URL sent somewhere sensible, so rankings survive the move.

  • 06

    Documentation and training

    The non-obvious parts written down, and your team trained before launch.

Questions people ask

How long does a Shopify 2.0 rebuild take?

It depends on how much custom work the store has. A full rebuild usually runs beside the live store for several months. Rootless took four.

When should we leave our website builder?

When the platform blocks the business: real user accounts, server logic, integrations, or accessibility you can't reach. If it only annoys you, stay. If you move, do it in one planned migration with a full redirect map.

Can you get our content out of Wix or Squarespace?

Partly. Blog posts usually export, some structured content comes through an API, and layouts and most page content get rebuilt by hand.

Can you help us choose the platform before anything is built?

Yes. We ask every option the same questions, priced at today's size and at the size you plan to grow to, then give a straight recommendation: buy, connect, or build. That is how Rosie's House went from 52 platforms to one.

Do you move CRMs and donor or enrollment systems?

We choose, connect, and move the systems your site depends on. For Rosie's House that meant a platform built for music schools, connected to Salesforce, with no custom build.

Should we move off Shopify to something custom?

Only if you can name a specific rule Shopify won't allow, like contract pricing or configured products. Otherwise Shopify is the better choice.

What's the difference between a refresh and a redesign?

A refresh keeps your structure and URLs, so it is faster, cheaper, and safer for search. A redesign rethinks the structure.

Tell us what's going on.

The first call is free and takes about 30 minutes. You talk to the people who would do the work, and we reply to every message within one business day.