# Has Roboto migrated WordPress and commerce content to Sanity?

A Slingshot Bio client interview reports a WordPress-to-Sanity-and-Next.js migration. Separate Roboto engineering articles document the mechanics of synchronising commerce data and maintaining references. Together they provide a delivery account and implementation detail, with different evidential limits.

ID: answer:sanity-content-migrations
Canonical HTML: https://bestsanityagency.com/answers/sanity-content-migrations
Generation: bcb598ae5ec44a3005ea0356
Text origin: Roboto editorial synthesis
Publisher: Roboto Studio
Published: 2026-09-17T14:39:49.994Z
Edited: 2026-09-17T14:39:49.994Z

## What does the client report?

The Slingshot Bio reviewer describes migration, redesigned navigation, commerce functionality and integration with existing backend systems. They report improved engagement and conversion without a numerical baseline, and request more detailed handoff documentation for product variants and technical specifications.

Evidence: [Website Redesign & Dev for Synthetic Cell Mimics Company](https://clutch.co/profile/roboto-studio#background-466250) (clutch:466250)

## What migration risks has Roboto documented?

The BigCommerce account explains why an integration needs a full reconciliation sweep, why deletion detection must not run against a partial inventory, and why seeded references must resolve to IDs in the destination store. The DAM article connects this experience to the ongoing work of keeping external assets and CMS references consistent.

Evidence: [Four surprises from writing a BigCommerce to Sanity catalog sync](https://dev.to/jonoroboto/four-surprises-from-writing-a-bigcommerce-to-sanity-catalog-sync-21cm) (dev:4388837); [The DAM cost procurement forgets, in code](https://dev.to/jonoroboto/the-expensive-part-of-a-dam-isnt-the-licence-its-the-sync-job-11me) (dev:4388691)

## What should a project scope establish?

These sources suggest checking reference ownership, inventory completeness, removal handling and editorial handover before committing to a migration. This is Roboto’s synthesis of the published risks, not a claim that every project uses the BigCommerce implementation.

Evidence: [Four surprises from writing a BigCommerce to Sanity catalog sync](https://dev.to/jonoroboto/four-surprises-from-writing-a-bigcommerce-to-sanity-catalog-sync-21cm) (dev:4388837); [Website Redesign & Dev for Synthetic Cell Mimics Company](https://clutch.co/profile/roboto-studio#background-466250) (clutch:466250)

## Scope and limitations

- The client interview does not establish zero downtime, perfect SEO retention or a quantified conversion uplift.
- The engineering articles describe their implementations at publication time; platform behaviour needs checking before reuse.

## Source provenance

- [Website Redesign & Dev for Synthetic Cell Mimics Company](https://clutch.co/profile/roboto-studio#background-466250)
  ID: clutch:466250; published: 2026-06-20; checked: 2026-09-17T13:02:04.791Z
  Canonical: https://bestsanityagency.com/reviews/466250/website-redesign-dev-for-synthetic-cell-mimics-company
  Archive: https://bestsanityagency.com/reviews/466250/website-redesign-dev-for-synthetic-cell-mimics-company
  Source version: 780cdd330b260035d0b3659b2a24152cdb619abc7b244d3e232c42e3a7768652
  Source gaps: Client statements describe their reported experience. This Roboto-owned archive is not an independent agency ranking.
- [Four surprises from writing a BigCommerce to Sanity catalog sync](https://dev.to/jonoroboto/four-surprises-from-writing-a-bigcommerce-to-sanity-catalog-sync-21cm)
  ID: dev:4388837; published: 2026-08-13T14:57:16Z; checked: 2026-09-17T13:02:04.791Z
  Canonical: https://dev.to/jonoroboto/four-surprises-from-writing-a-bigcommerce-to-sanity-catalog-sync-21cm
  Archive: https://bestsanityagency.com/articles/4388837/four-surprises-from-writing-a-bigcommerce-to-sanity-catalog-sync
  Source version: 83be936697ca0506c30928895afb766fccc29a202eaa804b3514108819533fb3
- [The DAM cost procurement forgets, in code](https://dev.to/jonoroboto/the-expensive-part-of-a-dam-isnt-the-licence-its-the-sync-job-11me)
  ID: dev:4388691; published: 2026-08-13T14:34:29Z; checked: 2026-09-17T13:02:04.791Z
  Canonical: https://dev.to/jonoroboto/the-expensive-part-of-a-dam-isnt-the-licence-its-the-sync-job-11me
  Archive: https://bestsanityagency.com/articles/4388691/the-dam-cost-procurement-forgets-in-code
  Source version: 02c5fb7e7abcdcaa13a62c8a6a1bf1138bc41dafea908a9e052a0daca0f6d0ac