Migrating to Shopify from Drupal

Our baseline migration includes product catalog exports (if using Drupal Commerce), content nodes (pages, articles, blog posts), media and images, taxonomy terms, menus and navigation, customers, and a prioritized window of order history. We also migrate available SEO metadata and social images. Exact fields, node types and record counts are confirmed during Discovery and documented in the SOW.

Drupal Commerce product types, product variations and custom attribute structures are analyzed in Discovery. Fyresite maps product variations to Shopify variants where possible and uses Shopify metafields or metaobjects, custom apps, or theme logic for complex product relationships like kits, bundles or build-to-order flows so that product selection, inventory and orders behave correctly.

Drupal content types and views are mapped to Shopify constructs. Standard landing pages and marketing content become Shopify pages or sections. For content-heavy use cases we use metafields, metaobjects or headless content strategies to preserve content structure and renderability. Views and lists are reimplemented as Liquid templates, sections or client-side queries depending on the desired UX.

Taxonomy vocabularies are migrated into Shopify collections, tags, or structured metafields depending on SEO and navigation needs. Menus and navigation structures are recreated as Shopify navigation and collection scaffolding to preserve findability and UX.

We create a URL mapping and 301 redirect plan for product, taxonomy and content URLs. SEO metadata is migrated where available. We run pre-launch and post-launch crawls to remediate broken links and verify canonical and hreflang rules when relevant.

User records can be migrated, but password hashes from Drupal may not be directly portable to Shopify. Standard practice is to migrate user accounts and trigger secure password reset flows or login invitations so customers can set new credentials. The customer experience and timing are documented in Discovery.

Yes, order migration is scoped during Discovery. Clients commonly select a rolling window such as the last 12–24 months but other ranges are supported. Order number preservation, tax and accounting reconciliation, and returns mapping are planned to avoid downstream operational issues.

Custom module logic is reviewed in Discovery. Fyresite follows a native-first approach: we replicate functionality with Shopify native features or vetted apps when possible. Where parity cannot be achieved, we propose custom Shopify apps or middleware to implement required business logic.

Forms and gated workflows are reimplemented using Shopify forms, apps or a lightweight custom app depending on complexity. Memberships or gated content are scoped and mapped to Shopify Plus B2B primitives, apps or headless session management as required.

For headless Drupal setups we evaluate whether to maintain a headless approach using Shopify Storefront API or Hydrogen, or to move to a theme-driven Shopify Online Store 2.0. We document tradeoffs for performance, editorial control and developer effort. Hydrogen or a custom storefront can be used when a headless PWA experience is required.

Subscription and recurring billing solutions are vendor-specific. We assess feasibility during Discovery. Tokenized payment data and subscription contracts often require provider collaboration or a migration plan to a Shopify-compatible subscription platform.

Integrations are planned in Discovery. Fyresite commonly uses middleware or custom connectors to handle inventory, pricing, order sync and PIM reconciliation. We define error handling, logging and reconciliation responsibilities in the SOW.

Shopify checkout is SaaS-managed. Theme styling and supported Shopify checkout settings are included. Deep server-side checkout customizations require separate scoping and are implemented only where Shopify Plus allows extensibility. Payment gateways are configured on Shopify and payment tokens are typically not portable between providers.

Timeline depends on content volume, catalog complexity, integrations and custom functionality. Typical engagements run several months. Complex enterprise migrations involving multi-site consolidation, heavy integrations or bespoke features commonly require longer schedules. Discovery produces a firm timeline.

Fyresite executes an agreed phased delivery: Discovery, Design and Development, QA and UAT, Launch, and hypercare. We define launch readiness criteria, cutover steps, and rollback contingencies in the SOW. Post-launch hypercare and training are included so your teams can operate the storefront.

Common exclusions include Drupal server-side custom modules that cannot be reasonably replicated, unsupported checkout engine modifications, large-scale BI or data warehouse replacements, and ongoing Drupal maintenance. Any out-of-scope items are documented and handled via Change Order if requested later.

Provide access to Drupal admin and database exports, a catalog of modules and integrations, example content types, sitemap and analytics access. Also provide a list of third-party providers and any regulatory or localization requirements to ensure accurate scoping.

Multi-site Drupal setups are evaluated in Discovery. We recommend mapping strategies such as a single Shopify Plus instance with Markets, multiple Shopify stores, or a hybrid headless approach depending on localization, inventory and operational needs. Tradeoffs for content duplication and integration complexity are documented.