1. Take an inventory before moving
List your products, variants, collections, images, customers, historical orders, discounts, and integrations. Export a backup from your current platform and note which records the destination import tools support.
2. Map the differences
Check how product options, handles, taxes, shipping rules, and customer data translate into Lulu. Start with a small import and verify it before moving the full catalog. Customer passwords generally cannot be moved as readable passwords.
3. Build while the existing store stays open
Prepare your theme, navigation, payment account, shipping rules, and policy pages on your new store address. Use a preview and keep your current domain pointing to the existing shop until the new one passes testing.
4. Plan URLs and search visibility
Record important existing URLs and map changed pages to appropriate destinations. Configure supported redirects and check page titles, descriptions, image text, and sitemap behavior. Avoid changing every URL without a reason.
5. Reconcile and test
Check counts, product prices, stock, variants, customer access, taxes, discounts, and delivery. Test a complete order and the follow-up workflow. Arrange help for integration-specific behavior before your launch date.
6. Switch deliberately
Pick a quieter period, reconcile recent changes, update DNS, and monitor both order queues while DNS propagates. Keep backups and a documented rollback plan. Verify your email and support links after the switch.
Explore the Lulu platform, compare packages, or ask the team about your setup.