We move you · Migration playbook · Included with Store and Brand
Most Indian businesses that come to Dwize are not buying a first website — they are leaving a broken one. WordPress that no one patches. Shopify that adds platform fees and app sprawl as revenue grows. A freelancer who vanished after invoicing. Dwize moves you off that, into a written operating year, without you doing the work.
You’re on
We move you
15 business days
You arrive at
Care Year monthly cadence begins from the cutover report.
The diagnosis
We have walked enough Indian MSME web stacks to know the four shapes of digital disappointment. One of them is probably yours.
Shape 01
A WordPress install three plugin-versions out of date. Forms broken, security warnings, freelancer last touched it 18 months ago. You know it is bad; you do not know who to ask. Most asked symptom: slow loads, contact form silently failing.
Why not WordPressShape 02
Shopify works. But the subscription is only the software layer. Serious stores still carry third-party transaction fees, paid apps, implementation labor, GST workflows, and operating fixes. That is when the migration math becomes worth reviewing.
See the Shopify fee mathShape 03
A freelancer or small agency built it 2-4 years ago. Took payment, launched, and slowly stopped responding. The site still works mostly. Nobody at the vendor end knows the codebase. You are now the unpaid integration tester.
Shape 04
A Wix or Squarespace template that gives the appearance of presence without the substance. No real schema, no real Indian payment integration, no real maintenance — just a hosted page. Customers searching specifics about your business find nothing.
Before and after
Drag the line to compare a neglected website with a Dwize surface. Illustrative layout, not a real client site.
Before: a neglected website with tiny text, a plugin update warning, a broken image and no WhatsApp button. After: a clean Dwize website with a one-line headline, WhatsApp and call buttons, services, a map and GST-inclusive prices. The list below states each change in words.
What changed
What “we move you” covers
Migration is not a CSV dump. It is a structured handoff of every customer-facing artefact and every commerce primitive. The Dwize team carries the file end-to-end — you do not project-manage the move.
Care Year covenant 04 (dedicated Dwize team) applies during migration too: a clear delivery lead, WhatsApp/email path, and a clear response path honoured through the move.
Products, variants, collections, inventory state, search-friendly URLs. Mapped to the Dwize Store schema, validated against your current data.
Customer records, contact details, and order history are reviewed for a clean, portable migration path.
Past orders, refund records, shipping data, GST invoice records. Imported with timestamps preserved so reporting continuity is intact.
Your domain stays at your registrar. Dwize provisions the required DNS records. You retain registrar-level access throughout.
Page copy, blog posts, images, brand assets. Migrated as-is, then audited together for any cleanup the new platform supports.
301 redirects from old URLs (where structures differ), preserved canonical structure, fresh sitemap, fresh JSON-LD on every page.
Public routes preserved
Migration is successful only when the paths people already use still land on a clearer surface. Search, social, and WhatsApp should feel continuous, not like a rebuild nobody explained.
Search and maps Old discovery paths point to the new trusted surface. 
Profile traffic Bio links and campaign links remain purposeful. 
Inquiry handoff Chats keep leading to the right product or order path. Migration cadence
The operating tempo of a Dwize migration. Each stage has a clear lead, a written deliverable, and a date. No fuzzy “in progress” status.
Stage 01
Day 0–2
Dwize audits the current site: stack, content volume, integrations, SEO state, payment configuration. Surfaces any blockers (e.g., active subscriptions, custom plugins) in writing.
Deliverable: One-page migration assessment, sent over WhatsApp or email.
Stage 02
Day 2–5
Catalog, customer, and order-history fields are mapped from the source platform into the new Dwize Store or Brand structure. Edge cases are flagged: SKUs without GST treatment, customers without phone numbers, orders missing shipping data.
Deliverable: Mapping document with field-by-field translation rules.
Stage 03
Day 5–10
New Dwize Store / Brand built on staging URL. Theme adapted to brand identity. All integrations configured (Razorpay, Shiprocket / Delhivery, WhatsApp Business catalog, ONDC if applicable). Test orders run end-to-end.
Deliverable: Working staging URL, ready for buyer review.
Stage 04
Day 10–12
Final data sync from the source platform. DNS update on the buyer’s registrar. Old URLs are redirected where needed, subscription/contact notices are handled where relevant, and the new site goes live.
Deliverable: New site live on the buyer’s canonical URL; old site offboarded.
Stage 05
Day 12–15
End-to-end test: search rankings checked, redirects verified, payment flows tested, GST invoicing verified, ONDC seller integration checked if applicable. Any drift surfaced and fixed.
Deliverable: Written cutover report; Care Year monthly cadence begins from this date.
Photo · NOIRLab HQ Server Racks — NOIRLab/NSF/AURA/T. Slovinský, CC BY 4.0
Ownership clarity
The most common fear about leaving any platform is the one Dwize answers in writing first. Migration is the one moment when ownership boundaries are easiest to muddy — we make them explicit before the move begins.
Stays at your registrar, in your name. Dwize never holds your domain.
Including DNS root access — you retain full registrar-level control throughout.
Logo, colour, copy, photography — all yours. Dwize licenses platform code, not creative.
Your creative assets, content, data, and agreed exports stay portable at year-end.
Tenant-isolated in the Dwize platform. Exportable any time, on request, in standard formats.
Data residency: India. No transfer to overseas processors without explicit consent.
Yours, in full, exportable. Razorpay payout records stay in your Razorpay account directly.
Dwize never sees raw payment-card data — that is Razorpay’s scope.
Pricing
Included free
Store · BrandMigration is part of the year you bought. No separate invoice, no scope-creep add-ons. The Dwize team that carries your Care Year carries your migration file too — same covenants, same contract.
Standalone migration
For buyers who want the move executed cleanly but are not yet ready to commit to a Care Year. We assess the source stack, write the scope, quote the one-time move, and make the handoff clear. No ongoing operations — that is what the Care Year is for.
Before the move
More answers on the FAQ, or compare the platforms: Why not Shopify · Why not WordPress.
We move you
We plan the move. One direct conversation, WhatsApp or email. Send the URL of your current site and a one-line description of what is broken. We come back with a written assessment and a stage-by-stage plan.
