What an ecomm migration to Nexcess looks like

Before the migration call

The conversation usually starts with one of two things: a hosting invoice that didn’t match the budget, or a vendor security review that exposed a documentation gap. A payment processor or enterprise retail partner asks for PCI scope documentation, hardware isolation confirmation, and a written responsibility model. When the current environment can’t produce those in the format needed, “we should probably do something about the hosting” becomes an active scoping conversation.

The first call happens before any work is scoped. What gets established early is the documented responsibility model that will be in place after the migration. For the developer or IT lead, that’s the question they’re carrying into the room. For the business owner, it’s what they’ll hand to the next vendor review. Getting it in writing before anything moves is a different kind of assurance than hoping the documentation materializes after.

One thing worth knowing before prep work begins: PHP and database versions need to be current on the source environment, and the destination needs roughly 20% more disk capacity than the current footprint. These don’t surface as surprises if the scoping call covers them.

The cutover window

The cutover gets scheduled for a low-traffic window with a buffer before the next major promotional event. For a store with transaction volume, that buffer isn’t flexible.

The migration is managed by Nexcess specialists. What your team’s time goes toward is access coordination at the start and QA at the end. The QA step matters more than it sounds: Nexcess sets up the destination environment, handles the data move, and then hands it back for testing because you know the custom logic better than they do. That handoff is deliberate. It’s also the step most merchants underallocate time for.

DNS propagation is last. Downtime during the cutover window is expected and the timing should be planned around your transaction calendar, not your developer’s availability.

Thirty days in

The compliance documentation exists in a format that can be handed directly to a payment processor or enterprise partner, not a conversation to schedule a document. For the ecomm director, this is usually what shows up first: the vendor review that previously required a three-week project gets handled in an afternoon.

Support works differently than most of what came before. When something surfaces at the application layer, escalation reaches engineers who know Magento, WooCommerce, or Shopware specifically. It’s a different conversation than routing through a generic infrastructure queue while checkout is degrading.

The December invoice looks the same as October’s. For whoever carries the finance responsibility, that predictability has a different kind of value than any feature comparison captures.

What doesn’t get talked about much is that the first month is mostly unremarkable. The store runs. Support is there when it’s needed. The compliance documentation is there when someone asks for it. The specific anxieties that built up between “we’ve decided” and “we’ve signed” don’t arrive.

That’s an unglamorous description of a successful ecomm migration. It’s also an accurate one.