How to Migrate a Product Catalogue to a New Platform with OpenClaw
Migrate a product catalogue with OpenClaw and ToolRouter. Run catalogue extractions on a schedule during staged migrations and sync data across platforms.
Tool
OpenClaw handles staged migrations where the old and new storefronts run in parallel for a period — re-running `scrape_catalogue` on the source store and syncing any changes to the new platform until cutover. This is the right approach for large catalogues where a single bulk import isn't practical.
Connect ToolRouter to OpenClaw
1Install the CLI
npm install -g toolrouter-mcp2Call tools directly from OpenClaw
toolrouter-mcp call web-search search --query "AI tools"
toolrouter-mcp toolsSteps
Once connected (see setup above), use the Catalogue Scraper tool:
- Define source storefront URL, target platform, and shared product schema.
- Run `catalogue-scraper` with `scrape_catalogue` on the source storefront on a schedule.
- Diff each extraction against the previous run and push only changed products to the target platform.
- Maintain sync until you are ready to cut over, then run one final full extraction.
Example Prompt
Try this with OpenClaw using the Catalogue Scraper tool
Use catalogue-scraper to extract products from https://mystore.com every hour during our migration. Diff against the previous run and sync only changed products to our new BigCommerce store. Keep this running until we cut over, then do a final full extraction for reconciliation.
Tips
- Sync changes frequently during the migration window — stale data between old and new is where customer-facing bugs appear.
- Use `sku` as the shared identifier between platforms so diffs are reliable.
- Do one final full extraction at cutover and reconcile against the new platform to catch any sync gaps.