Audit of the store you run today
Every app, theme edit and manual workaround on the current store is listed, and each is marked to be built into the new store, connected to it, or dropped.
Replatforming is moving a live store off Shopify, WooCommerce or Magento onto software written for it, carrying the products, customers and order history across and keeping the addresses search engines already rank. It is for merchants who have outgrown a platform's rules or the apps that fill its gaps. Ozwebnet writes the new store from scratch in Adelaide, South Australia, for businesses across Australia; you receive the source code with the IP assigned to you, under one fixed quote staged against milestones.
DETAIL OF SHEET 05 — ONLINE STORES →
Replatforming is rebuilding a store that already trades — on Shopify, WooCommerce, Magento or another hosted platform — as software written for that business, then moving the live trade across. The catalogue, customer accounts and order history are exported from the old platform, cleaned and loaded into the new store's own database. Every product and category address is mapped to its new home, so the pages search engines already rank keep resolving. The old store keeps trading until test orders pass on the new one, and the domain is switched in one planned cutover.
Every app, theme edit and manual workaround on the current store is listed, and each is marked to be built into the new store, connected to it, or dropped.
Catalogue, variants, images, customer accounts and past orders are exported from the old platform, cleaned and loaded into the new store's own database. Where the old platform will not release password hashes, returning customers set a new password on first login and the store tells them so.
Every product, category and content address on the old store is mapped to its new address and redirected, so pages that already rank and links in old emails keep resolving.
The gateway you already use and the shipping rates and zones you charge today are set up on the new store, so checkout and delivery charges work as they do now.
What the old apps did between the store and Xero, MYOB, your warehouse or your email marketing tool is rebuilt as direct connections from the new store to those systems.
The old store keeps trading while the new one runs on a private address with a fresh copy of the data; staff place, pay, pick and refund test orders until they pass.
The last export is loaded, the domain is pointed at the new store and the redirects go live in one planned cutover; once live orders are flowing, the old platform can be closed.
TYPICAL SCOPE FOR THIS KIND OF SYSTEM — YOUR EXACT SCOPE IS FIXED IN WRITING AT THE SPECIFICATION STAGE.
Not sure which? Ten minutes on 1300 699 321 tells you — Mon–Fri 9–5 ACST.
One fixed quote, set in writing at the specification stage (02 Blueprint) and staged against the five milestones below. Each milestone ends with a working system; stop at any milestone and keep what has been built.
SEE THE FIVE STAGES ANIMATED →We list what the current store does — every app, theme edit and workaround — and take a first export of its data.
The new store, the data to carry across and the URL map are specified in writing; the fixed quote is set here.
Built against a copy of your live data while the old store keeps trading; each milestone ends with a working store.
Migrated records are checked against the old platform, every redirect is tested, and test orders are placed, paid and refunded on the private address.
The domain is switched in one planned cutover, and you receive the source code with the IP assigned to you.
Every product, category and content address on the old store is mapped to its new address and redirected, so the pages that already rank keep resolving. No ranking can be promised; what is in scope is a redirect for every old address.
Yes. The new store is built and tested on a private address against a copy of your data, and the domain is switched in one planned cutover once test orders pass.
Customer accounts and order history come across. Where the old platform will not release password hashes, returning customers set a new password on first login, and the store tells them so.
One fixed quote, set in writing before the build and staged against milestones.
Yes — source code delivered, IP assigned to you. The store is yours to change, move or hand to another developer.
Call, or answer a few short questions — what you run, what breaks, when you need it working — and we reply within one business day. The quote is fixed in writing before any build starts.