Before we plan anything, we go through your Drupal store in detail, including the custom fields, content types and the way customers actually buy. Then one team handles the rest. We migrate the agreed data, build your Shopify storefront, connect your integrations and run the launch. By the time you go live, everything on the plan has been built and tested.
or call 888-711-2347
Includes 60 days of free post-launch migration support. We're still here after the move.
Official Shopify Partner
Since 2015 · Shopify store migration, design and development. View profile ↗
Illustrative workflow, not a live project
Attention: 6 items need attention.
Does nearly every change to your store need a developer?
Drupal Commerce presents itself as a framework-first toolkit for developers to build with. Agency comparisons say module setup, theming and integrations usually take technical skills, so merchants running it often lean on an in-house team or an agency even for routine changes.
Think about how often small requests sit in a developer queue, and who you'd call if your current developer disappeared. Shopify's admin lets non-developers make many everyday changes, although deeper custom logic can still call for apps or a developer.
Have Drupal version upgrades turned into a project that keeps coming back?
Commerce releases follow Drupal core versions. The drupal.org page lists 3.x for Drupal 10.3 and 11, 2.x for Drupal 9.3 and 10, and 1.x for Drupal 7. Drupal 7 support ended in January 2025, and the vendor behind Commerce sells upgrade assessments because the cost depends on the version you run today.
If your store sits on an older line, a major upgrade is a project in its own right. Put the cost and risk of that upgrade next to the cost of rebuilding on a hosted platform where core updates are handled for you.
Are patching, hosting and uptime all on you?
Drupal Commerce is self-hosted, so you or your agency pick the host, look after the database and apply security updates. Comparison articles say that suits teams with dedicated technical resources. One Drupal.org issue describes a store where an unplanned Composer upgrade between Commerce releases meant days of cleanup.
Ask who applies updates, who watches the server, and what happens during a traffic spike. A hosted platform hands much of that to the vendor, but you give up server and database access.
Does every extra feature add another module to vet and maintain?
The core project covers products, variations, order types, promotions, a payment API and tax support. The project page lists recurring billing, shipping, stock, PayPal and AvaTax as contributed modules. Quality and upkeep vary, and sources suggest checking a module's maintenance status before you rely on it.
Write down every module your store depends on and how current each one is. On Shopify, similar features usually come from built-in tools or apps, which have their own subscription costs and deserve the same scrutiny.
Is a free license really cheaper once hosting and development are added?
Drupal Commerce has no license or subscription fee, though comparison articles point out it takes upfront development, hosting and ongoing maintenance. Some of them argue the total can still come out lower for complex stores.
Add up a year of hosting, developer hours, security monitoring and upgrade projects, then set that against a Shopify plan plus apps and transaction fees. How custom your store is changes the answer a lot.
Is your store simple enough that most of this flexibility goes unused?
Drupal is built around content, and migration agencies note that store elements end up spread across nodes, fields and custom entities. That flexibility helps with custom content models, yet some merchants report using only a small part of it.
If your catalogue is straightforward, all that flexibility may add overhead and no revenue. If you depend on complex editorial workflows or custom content relationships, keep in mind that Shopify's content tools are more limited and may need metafields, metaobjects or an app.
Pet supplies
Advance Pet Mart started on WooCommerce, but plugin and hosting problems kept getting in the way. We moved the store to Shopify, and they are very happy with the move. We also worked with them on design, SEO, AI SEO and marketing.
Visit the live store
Electronics & gaming retail
We moved City of Games from a broken OpenCart store to Shopify in four weeks, kept its look, rebuilt the features it had lost and protected its search rankings with 301 redirects.
Read the case study
We moved Contours Rx from BigCommerce to Shopify and redesigned the website with a sleek, user-friendly interface and enhanced product pages.
Visit the live storeMove and rebuild. For stores that need their data moved and a new storefront built on Shopify.
Quote after a free store review
Move a complex business. For large or heavily customized stores with connected systems.
Custom quote after discovery
Included in every migration. Redirects for your old URLs, titles and descriptions carried over, and 60 days of free support after launch. Your Shopify plan, apps and other third-party costs are not part of our quote.
SKUs, pricing and media files
What they mean and what they connect to
Terms and navigation
Rebuilt to behave the same
Pictures and documents
Content in other languages
Profiles and account details
The date range we agree on
Links to products kept
Pricing rules rebuilt
Scoped on their own
A redirect map we test
What we propose for each item, and the main check before launch.
| Drupal Commerce | Where it goes in Shopify | What we check |
|---|---|---|
| Products & variations | The products, variants and structured fields you approve. | SKUs, valid option choices, links, prices and whether an item is active. |
| Custom fields & references | Metafields, metaobjects or rebuilt content, whichever fits. | What the data means and how it connects, beyond the field names. |
| Drupal Commerce | Where it goes in Shopify | What we check |
|---|---|---|
| Taxonomy, menus & listings | Collections, navigation and the content structures you approve. | Product categories kept apart from editorial tags. |
| Media & translations | The files and translated content you approve. | Access, matching, formatting and the assets linked to each item. |
| Reviews, articles & custom content | The pages and blog posts you approve, or a compatible app. | Access, links to other records and whether anything is missing. |
| Drupal Commerce | Where it goes in Shopify | What we check |
|---|---|---|
| Users, profiles & customers | The customers and addresses you approve, with their account details. | A Drupal user isn’t always a customer, or a marketing subscriber. |
| Historical orders & items | A supported import, or an archive you keep. | Original totals, adjustments, references, dates and statuses. |
| Memberships, licenses & recurring records | A transition scoped on its own, or a service that stays where it is. | Entitlements, renewals, billing and access. |
| Drupal Commerce | Where it goes in Shopify | What we check |
|---|---|---|
| Pricing & promotions | The agreed pricing behavior, rebuilt. | The calculated result, who qualifies and which rule wins. |
| SEO aliases & metadata | A map of old to new URLs and redirects we test. | Public paths, old aliases, translations and Shopify's limits. |
Imported history doesn’t carry over the original payments or replay past events. Customer passwords, stored payment credentials, exact order numbers and identical reports shouldn’t be assumed to come along. Source references can be kept through a supported method.
Some information imports straight into Shopify. Some functionality has to be rebuilt. Some records are better left in an archive, and a few things, like memberships or a retained Drupal site, get their own scope. Your proposal says which is which.
Which versions you run, plus exports, APIs and custom entities.
Products, content types, media and translated pages.
Calculated prices, checkout steps and order workflows.
ERP, PIM, fulfillment and anything else you connect.
Moving everything, or keeping Drupal for content.
Acceptance checks, the cut-off and a final reconciliation.
The proposal keeps our project fee apart from the Shopify subscription, apps, themes, retained Drupal hosting, payments and other third-party costs. Price and schedule are confirmed once the review is done.
FreeStore review and quote before you hire us
60 daysFree post-launch migration support included
Tell us what the site sells, which content matters and what you'd like to fix. We go through the store and the content around it, then tell you what moves, what gets rebuilt, what could stay in Drupal and what the project costs.
You don't need technical knowledge or your version numbers. We don't need exports or logins to start, and secure access is arranged later.
Drupal 7 and Commerce 1.x builds often use display nodes and product relationships that look very different from Commerce 2.x and 3.x.
Checked by version generation.Ubercart is a separate commerce system for Drupal. A Drupal site isn't necessarily running Drupal Commerce.
We confirm the module before anything else.Product and order types, content types, contributed and custom modules, and any custom code that affects how you sell.
Listed before we map anything.The exports, APIs, database and files we can reach, plus any ERP, PIM, fulfillment and identity-provider connections.
You don’t need exports to begin.These are milestones for specific versions. Drupal Commerce itself isn't shutting down.
Upgrading Drupal, or paying for commercial extended support where it applies, can also be the right call. Dates checked October 20, 2026 against the official Drupal release schedule ↗ and the Commerce project page ↗.
Selling and agreed content move to Shopify
Shopify handles selling and Drupal keeps the content
Headless setups aren't automatically required, cheaper or simpler. If Drupal stays, so do its hosting, updates, security and maintenance, and you end up running two systems. A Shopify module listed on Drupal.org isn't automatically official, secure, maintained or production ready, so we check any module before we recommend it.
| In your Drupal store | What we review | How we decide the Shopify setup |
|---|---|---|
| Products & variations | SKUs, options, prices, media, active status and which combinations actually exist. | Products and variants that match what you really sell, with no duplicate product for every record. |
| Display pages & product links | Display nodes or product pages that point to purchasable records, which is common in Commerce 1.x builds. | One product page per item, with the page content and the purchasable record joined on purpose. |
| Custom fields & references | Fields on products, variations and attributes, plus links to guides, documents and related items. | Metafields, metaobjects or rebuilt content that keep the relationship, instead of copied Drupal IDs. |
| Personalization & custom items | Customer input, order-item fields and any custom purchasable entities that aren’t ordinary variants. | A field, an app, scoped development or a retained service, chosen item by item. |
| Stock & fulfillment | The stock module, custom logic or outside system that really owns availability, and how it feeds fulfillment. | Quantities, reservations and who updates them, agreed for Shopify without assuming a standard stock field exists. |
The example on the right is illustrative and not a client result. Your mapping comes from your own content types and fields.
| Display page content | Trail Jacket |
|---|---|
| Variation purchasable | TJ-BLU-M · $140.00 |
| Reference entity field | Guide: How to layer |
| Stock external system | Warehouse feed |
| Product | Trail Jacket |
|---|---|
| Variant | Blue / M · $140.00 |
| Related guide | Linked blog post |
| Availability | Agreed feed owner |
The guide is linked, not copied into the product, and stock keeps one clear owner.
One Drupal vocabulary can sort articles, products and documents. We map what each term is for instead of turning every term into a collection.
Product terms and editorial terms.Listings built in Views are rebuilt as Shopify collections, filters or templates that do what you agreed.
We rebuild the behavior instead of copying it.Paragraphs and Layout Builder pages don't turn into Shopify sections on their own. We rebuild the layouts you agree to keep.
Your content stays, the layout is rebuilt.Product records alone leave out pages, media, translations and documents. We inventory the whole site we can reach.
A list of everything on the site.Private content needs real access control. Member-only pages and documents need permissions that are actually enforced, and a hidden menu link doesn't count. We agree where each protected item lives, then test it with logged-out visits and the wrong account.
Prices that change with the customer, the company, the store or the date, checked against the total you expect.
Quantity breaks, promotions, taxes, shipping and fees, and the order they apply in.
Custom checkout steps, order types and state changes, rebuilt with supported features or scoped development.
Account roles kept apart from customer groups, plus company pricing and any approval steps.
| Drupal behavior | Shopify approach | Status |
|---|---|---|
| Trade accounts: $24.00 from 20 units | B2B setup or app, by plan | Review |
| Spring promotion: 15% off guides bundle | Shopify discount | Agreed |
| Checkout step: delivery date | App or scoped development | Test |
| Order state: awaiting approval | Workflow mapped first | Review |
| Price recalculation on old orders | Prevented in the import | Not allowed |
Old orders come in with their original values and are not recalculated as live carts. We plan the import so it can't send customer emails, create fulfillment requests, bill anyone or hand out licenses and access by mistake.
Shopify's B2B features depend on the plan. A Drupal role or custom checkout flow doesn't automatically have a Shopify equivalent, so we only recommend a plan and setup after reviewing what you need, and we check Shopify's current plan details at that point.
Which purchase or role gives which access, how that access expires and where it's enforced after launch.
Access is tested before launch.Providers, renewals, billing tokens and customer access, planned as ongoing services and not just imported as orders.
Renewals get their own plan.Where unfinished orders get completed, and who handles their fulfillment, refunds and returns.
Old payments may still need the old provider.We review balances, then agree whether they keep being redeemed, get replaced or get settled.
Nobody spends the same value twice.Past orders don't restart renewals, recreate software licenses or move stored payment credentials. Recurring billing and entitlements get their own agreed plan, and you keep the source and payment-provider access you need until every outstanding obligation is settled.
Brand layouts, product templates, navigation and editable content, or parts of your current design that you want to keep.
Explore theme & design →Scoped workflows and integrations for the cases where no existing app does the job.
Explore app development →The migration checks for URLs, content and metadata we agree on, with ongoing optimization as a separate service.
Explore Shopify SEO →SEO, Google Ads, Meta Ads, email and other channels that fit, to support growth after launch.
Explore ecommerce marketing →The migration is quoted on its own. Redesign, app development and ongoing marketing only come in if you want them, each with its own scope and price.
None of these come across on their own when a store moves. We check the feeds and tracking we agreed on, and test that private pages and files can't be opened without the right access.
Shopify has its own URL structure and some redirect limits, so we agree what coverage is realistic for your actual paths. Sending everything to the home page isn't a plan. We don't promise identical URLs, unchanged rankings or automatic traffic growth.
Example paths only. We work from your site’s real aliases, languages, redirects and file settings.
Connecting a domain to Shopify and transferring its registration are two different jobs. A domain you own can usually be connected without changing registrar. We check DNS and any subdomains first.
Shopify doesn't host email inboxes. If your mailboxes sit on the same hosting account or DNS as Drupal, we plan for them before anything changes.
If some content stays in Drupal, so does the hosting and its upkeep. If not, we hold on to the agreed backups and access until the dependencies are sorted, and then you decide when to close it.
We always arrange access to your Drupal admin, server and database securely, and never through the public enquiry form.
Migration tools can move common Drupal Commerce records, and some providers also sell assisted or managed services with a person behind them. If a tool suits your data, we'll use it as one part of the job. What we're responsible for is the whole agreed project around it, covering source review, mapping, content, storefront, functionality, testing and launch.
| Your question | Self-service migration tool | Migration managed by WEP |
|---|---|---|
| Who reviews the source? | You pick from the records the tool supports. | We identify core and commerce versions, custom entities, modules and content types, and write down what moves. |
| What about content and relationships? | Supported entities may move, while custom content and references are often left to you. | We list your content, map the references and rebuild listings and layouts as agreed. |
| What about prices and workflows? | Stored values may move, but calculated rules usually don't. | We look at what each rule is meant to do, then rebuild and test the ones you agree to keep. |
| Who builds the storefront? | Usually a separate job, left to you or another provider. | Theme setup or customization planned alongside the data and content. |
| Who runs the launch? | Your team coordinates the cut-off, domain, redirects and checks. | We run the cut-off, domain, redirects and late-order checks, then stay on for 60 days of free support. |
The online store migration was seamless without having 0 downtime. The staff is properly trained, well communicated and proactive Highly recommended
Web commerce pros created a really lovely design for our website. They also changed the layout for our images and updated/resized images so that the site is overall much more attractive. We have been receiving a lot of positive feedback from customers on the ease of use and the overall look of our site. In addition, we are very grateful to Roy for coming up with a creative solution for allowing customers to easily create their own quotes, which has been very helpful to both our operations and our customers.
Arfat and team were proficient with BigCommerce Page Builder and Shogun to create and modify pages. We successfully completed the migration with their assistance and were happy with their work. We would hire again soon for our next project.
We find out which core and commerce versions you run, along with your content, entities, rules, access and any systems that stay, and agree where each one ends up.
Where practical we build Shopify on the side, test sample products and content relationships, and ask for your approval against the acceptance criteria we agreed.
We agree how catalog and content changes are handled, the cut-off, which changing records get a final update and which system owns stock.
We handle the domain and integrations, then check late orders, inventory, retained content and access obligations before handover.
Examples of the acceptance checks in a Drupal project.
So launch day is planned in advance.
The migration runs around a defined cut-off and does not keep Drupal and Shopify syncing both ways. We reduce the risks as far as we can, but we can't promise zero downtime, zero data loss or compatibility with everything.
It depends mostly on how custom your store is, meaning the number of product types, custom checkout rules, integrations and languages. A simple catalogue moves faster than a heavily customised build. You get a realistic timeline after the free store review, not a generic number.
Yes. Your current store stays live while we build and test the Shopify store on the side. We then pick a quiet period for the switchover and sync recent orders. Zero downtime isn't something we can promise, but we plan to keep any gap as short as we can.
Custom module code does not transfer to Shopify. We write down what each custom rule does, then match it to a built-in Shopify feature, an app or a custom build. Some behaviour has no one-to-one match, and we flag those items during the free store review.
Yes. We go through your Drupal setup, modules, data and goals, then tell you what moves cleanly, what needs rebuilding and what the work is likely to involve. You're under no obligation to go ahead.
Our own team handles planning, data mapping, store setup and launch, and you get a single point of contact. You're involved for approvals and testing, but you don't have to do the technical work yourself.
Products, variations, orders, customers and content all sit in your Drupal database, so they can be pulled out through exports, database queries or migration tooling. Drupal keeps products and variations as separate entities, so we map them carefully into Shopify's product and variant structure. The free store review confirms exactly what's available.
In most cases they can be mapped, though not always one-to-one. Shopify limits how many options a product can have, so a product with many attributes may need restructuring, splitting or an app. We start with your most complex products.
Usually, yes. Historical orders can generally be brought into Shopify with migration tools or the API, and Shopify recommends importing products and customers first so orders link to them. They show up as past orders for reference and reporting and are not re-processed. Some details, such as certain custom order fields, may need to be stored differently.
Standard pages and articles can be moved or rebuilt in Shopify. Drupal content types with custom fields or relationships don't copy across directly, so we usually recreate them with metafields, metaobjects or an app. If your site is heavily editorial, raise it during the free store review.
No. Shopify states that passwords cannot be moved by CSV import because they are stored encrypted outside Shopify. Customers are invited to set a new password, or sign in through the account flow your new store uses. We'll help you word a clear message to them.
Yes. Names, emails, phone numbers and addresses can be imported, and Shopify's import rules handle duplicate emails. Shopify's customer import does not bring over total spent or total orders figures. After the import, we compare the results with your source data.
Not directly, because Drupal roles and permissions don't map to Shopify. Wholesale or trade customers are usually handled with customer tags, separate pricing or Shopify's B2B features where your plan includes them. We settle the best fit during the free store review.
Your URLs will change, because Shopify uses its own structure for products, collections and pages. We map old URLs to new ones and load 301 redirects, which Shopify supports through CSV import. Unchanged rankings aren't something we can promise, but we protect what we can and keep watching after launch.
No, because Drupal themes are built on a different system. We rebuild your design on a Shopify theme and keep your branding, layout priorities and content. Expect it to look familiar rather than identical.
Yes. Shopify supports multiple languages and markets, though translating everything may need an app or manual work depending on your setup. We go through your Drupal language configuration and tell you how it maps.
You'd pay for a Shopify plan, any paid apps you choose and payment processing fees, and you'd stop paying for your own hosting. Plans and fees change, so during the free store review we compare current Shopify costs with what you spend on hosting and developers today.
They don't carry over. Shopify offers its own payments in supported regions and many third-party gateways, plus built-in shipping rates and apps. What's available depends on your country, so we confirm your gateway and carriers early.
We quote after reviewing your content, data, workflows and integrations, so there's no fixed price or delivery date before the review. Shopify, app, retained hosting and other running costs are listed separately. Every migration comes with 60 days of free post-launch migration support within the agreed scope.
Tell us what the site does, what has to stay and what you'd like to improve. We'll go through the content and commerce requirements, then propose a scope, a next step and a quote.
Or call 888-711-2347
60 days of free post-launch migration support within the agreed scope.
