{"id":947,"date":"2026-08-10T08:05:32","date_gmt":"2026-07-02T10:02:44","guid":{"rendered":"https:\/\/quickshipd.com\/blog\/delivery-settings-site-migration-redesign\/"},"modified":"2026-09-03T09:03:26","modified_gmt":"2026-09-03T09:03:26","slug":"delivery-settings-site-migration-redesign","status":"publish","type":"post","link":"https:\/\/quickshipd.com\/blog\/delivery-settings-site-migration-redesign\/","title":{"rendered":"What Happens to Your Delivery Settings During a Site Migration or Redesign"},"content":{"rendered":"\n

A site redesign or hosting migration is stressful enough without discovering three weeks later that your delivery estimate quietly stopped showing up somewhere it used to. Settings-based plugins are generally safe across a migration, but \u201cgenerally safe\u201d isn’t the same as \u201cguaranteed,\u201d and this is exactly the kind of small feature that’s easy to forget to check.<\/p>\n\n\n\n

Here’s what typically survives a migration or redesign, and what’s worth verifying directly afterward.<\/p>\n\n\n\n

What Usually Survives a Standard Migration<\/h2>\n\n\n\n

A straightforward hosting migration \u2014 moving your entire WordPress database and files to new servers \u2014 typically carries your plugin settings along with everything else, since they’re stored in the same database. Your delivery days, cutoff time, holiday list, and display toggles should all transfer intact.<\/p>\n\n\n\n

\"delivery<\/figure>\n\n\n\n
\ud83c\udfaf NOTE<\/strong> This applies to a like-for-like migration \u2014 same WordPress install, moved to new hosting. A rebuild from scratch on a new platform is a different situation, covered below.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

What a Theme Redesign Can Actually Break<\/h2>\n\n\n\n

Switching themes, or heavily restructuring your product page layout with a page builder, is the scenario most likely to affect display \u2014 not because your delivery settings disappear, but because the theme hook your estimate was displaying through may have moved, changed, or been removed entirely in the new design.<\/p>\n\n\n\n

\"display<\/figure>\n\n\n\n

After a theme change, visit each page where you’d enabled display \u2014 product, shop, cart, checkout \u2014 and confirm the estimate is still showing up in a sensible position, not just that it’s technically still enabled in settings.<\/p>\n\n\n\n

\ud83d\udea7 IMPORTANT<\/strong> Don’t assume a theme change is complete until you’ve checked delivery estimate display specifically. It’s a small enough element that it’s easy to overlook during a broader visual QA pass focused on bigger, more obvious changes.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

What Doesn’t Survive a Platform Change<\/h2>\n\n\n\n

Moving off WordPress entirely \u2014 to a different eCommerce platform \u2014 means starting your delivery estimate configuration from scratch on whatever tool that platform supports, since QuickShipD<\/a> is a WooCommerce-specific plugin. This isn’t a migration issue so much as a full replacement, worth planning for separately if a platform change is on your roadmap.<\/p>\n\n\n\n

\n
Get QuickShipD Now!<\/a><\/div>\n<\/div>\n\n\n\n

Settings Survive, Display Needs a Check<\/h2>\n\n\n\n

Your delivery estimate configuration typically comes through a standard migration intact, since it lives in your database along with everything else. Display is the piece worth verifying directly, especially after a theme or page builder change that restructures your product page.<\/p>\n\n\n\n

A quick visual check across each enabled page after any major site change takes a few minutes and confirms QuickShipD’s estimates are still displaying as expected.<\/p>\n\n\n\n

\n
Get QuickShipD Now!<\/a><\/div>\n<\/div>\n\n\n\n

Related Reading<\/h2>\n\n\n\n