How to Transfer an OpenCart Store to WordPress and WooCommerce
Transfer an OpenCart store to WooCommerce with checks for products, customer accounts, order history, URLs and checkout. Explore the Niwa Business migration route.
To transfer an OpenCart store to WordPress and WooCommerce, create a separate WordPress installation, activate WooCommerce, and move your catalog through a compatible importer or mapped CSV files. Use a migration route that also supports customers and orders if you need that history. Rebuild the storefront and store settings, map old URLs to their new pages, then test the store and transfer any newly added data before switching your domain.
WordPress manages the website. WooCommerce adds the store. Moving your OpenCart database or uploading its theme files into WordPress will not create a working WooCommerce shop.
Move your OpenCart store with Niwa Business
You can handle the transfer yourself or use Niwa Business for the migration to WordPress. Niwa Business is USD 150 and includes a custom WordPress website or migration, hosting, maintenance and AI tools adapted to your business.
For an OpenCart store, define the migration scope before work starts: which products, customer records and orders need to move, which features need replacements, and how the final transfer will be checked. The USD 150 offer has an agreed migration scope. Any custom integrations, unusual pricing rules and extensive historical data you need must be included explicitly.
The service route follows the same checks described below: prepare WooCommerce on staging, transfer the agreed data through a compatible method, rebuild the storefront, test checkout and redirects, then reconcile new orders and stock before launch. Once the data has been moved, configure the Niwa assistant for daily work in the new store.
After migration, customers can ask Niwa about the catalog on the website or WhatsApp, get help choosing a product and use supported cart actions on the website. Niwa uses the same business context to complete connected sales workflows directly in WhatsApp conversations. The owner can use Niwa to update stock or edit product content in WordPress. These workflows start with the accurate product and variation data you bring across.
Discuss your OpenCart migration with Niwa. Include your public store URL, OpenCart version and the features you need to retain.
If you prefer to manage the transfer yourself, follow the steps below. Start with a list of what the existing store does. That list determines which migration method you need and what must be rebuilt.
1. Back up OpenCart and record what needs to move
Create backups of the OpenCart database and files, including product images and downloadable files. Keep a copy away from the live server and confirm how it can be restored.
Then record:
- Your OpenCart version and any modifications to its database.
- Products, categories, options, SKUs, prices, stock and images.
- Customer accounts, addresses, groups and order history.
- Coupons, reviews, information pages and downloadable products.
- Languages, currencies and any additional storefronts.
- Payment, shipping, accounting and other connected services.
- Existing product, category and information-page URLs.
Separate data from functionality. An order can be imported, but its payment integration needs a WooCommerce equivalent. A product option can appear in the new catalog while its pricing or stock behavior still needs work.
Give every item a destination: import it, recreate it, replace its integration, or deliberately leave it behind.
2. Prepare WordPress and WooCommerce on staging
Use a staging environment to build and test the destination while the OpenCart store remains available. Protect staging from public access and search indexing.
Install WordPress and WooCommerce, choose a suitable theme, and configure currency, location, payment methods and shipping. Document how taxes should behave in your store, then verify the configuration against representative orders.
You will need a new storefront implementation. OpenCart themes and extensions do not run as WordPress themes and plugins.
Before importing customer records, keep test emails and external automations from reaching real customers. A trial transfer should not trigger a batch of welcome messages, fulfillment requests or accounting updates.
3. Choose an import method that covers your data
There are three practical routes.
WooCommerce product CSV importer
Useful when: You mainly need a product catalog and can prepare its fields
Check before choosing: Customer accounts and order history require a separate route.
OpenCart migration plugin
Useful when: You have compatible source access and need more entities
Check before choosing: Edition, options, database requirements, password handling and repeat imports.
Migration service or custom transfer
Useful when: Your store has unusual data or several connected workflows
Check before choosing: Written entity coverage, exceptions, validation and final-data transfer.
The built-in WooCommerce CSV importer is a product tool. Export a sample WooCommerce product file to see the destination schema, map your OpenCart export to it, and save the file as UTF-8. Keep SKUs intact, including any leading zeros. Image links must be directly accessible, or the images must already be uploaded.
A plugin can handle a broader scope. For example, FG OpenCart to WooCommerce lists basic catalog and information-page import in its free edition. Customers, orders, options and several other functions are listed under Premium. Check the precise edition and add-ons your store requires.
Another option, documented on the WooCommerce marketplace, requires the OpenCart and WordPress databases to be on the same server. That is a requirement of that extension, not a rule for every migration.
Do not buy a tool until its supported version, access requirements and data coverage match your store.
4. Import a small sample and check the difficult products
Choose representative records rather than the easiest products alone. Include a simple product, a product with options, an out-of-stock item, a sale item and a downloadable product if you sell one.
For the FG importer, the documented starting workflow is:
- Activate WooCommerce and install the appropriate importer edition.
- Open Tools > Import > OpenCart.
- Enter the source database connection settings and store URL privately.
- Test the connection, review the selected settings and run the staging import.
If your importer supports selecting a sample, use that setting. Otherwise, test against a controlled source copy with representative data. Keep backups and avoid destructive destination-clearing options on a populated store.
For the CSV route, open Products > All Products > Import, upload the prepared file and review column mapping before running it. Variable products need parent and variation rows with the correct relationships. Start small enough that you can inspect every result.
Compare the imported records with OpenCart. Check descriptions, galleries, category placement, prices, tax classes, stock and selectable options. A successful import message does not prove all those fields behave correctly.
Example: checking a shoe with two sizes
Suppose a hypothetical store sells a black shoe in sizes 40 and 41, with three pairs of size 40 and five pairs of size 41 available.
The WooCommerce product should let a shopper select each size and use the correct stock for that selection. Verify how the source options map to variations or another supported product configuration. Adding eight pairs to a parent product would not preserve the size-specific availability.
Also test whether the price changes with the chosen option. OpenCart options and WooCommerce variations should not be treated as interchangeable without checking their behavior.
5. Transfer the full data and verify customer access
Once the sample is correct, create a fresh destination backup and run the full transfer using the tested settings.
Compare counts, but also inspect relationships. A thousand imported orders are not enough if they belong to the wrong accounts or have incorrect totals.
Review a selection of older and recent orders for dates, line items, discounts, shipping, taxes, currency, status and customer association. Decide how to retain original order references if the destination uses different IDs.
Customer passwords need an explicit plan. Some migration tools provide OpenCart password compatibility; other routes require account activation or password resets. Test the chosen behavior with an authorized test account before describing it to customers.
For downloadable products, check the file, download settings and account entitlement. Seeing the product in the dashboard does not establish that a returning customer can download a previous purchase.
If an import appears stalled, inspect its status and logs before starting another one. In a historical FG support thread, the author explains that repeated starts while an import is still running can create duplicates. Make sure the background process has stopped before retrying.
6. Map old URLs to the correct new pages
Build a list of old product, category and content URLs, then assign the corresponding destination page to each one. Keep existing addresses where practical. Where they change, configure permanent redirects to the equivalent content.
For example, an old OpenCart product URL such as index.php?route=product/product&product_id=123 might redirect to /product/black-work-shoe/. That is an illustration, not a redirect rule to copy into every store. Query-string URLs need a redirect method that handles their parameters correctly.
Avoid sending every old URL to the homepage. Check internal links, canonical URLs and the new sitemap, then test the redirects for loops and chains.
Google advises mapping URLs, testing the destination and monitoring the move. Rankings can fluctuate while pages are recrawled, so redirects cannot support a promise of unchanged rankings. See Google's site-move guidance.
7. Test checkout and plan the final data transfer
Run through the shopping journey on desktop and mobile:
- Find a product, select its options and add it to the cart.
- Change quantities and verify stock limits.
- Check shipping for representative delivery addresses.
- Apply relevant coupons and compare totals.
- Test guest checkout and a returning-customer account.
- Use the payment provider's supported test mode to check success and failure.
- Verify order emails, stock changes and fulfillment connections.
Then account for what changed in OpenCart while you were building WooCommerce. New orders, accounts and stock updates must not disappear between the initial transfer and launch.
Choose a final synchronization or a controlled checkout pause, according to the capabilities you have tested. Record which orders have already been fulfilled and which remain open. Avoid processing the same order through both stores.
A tool that copies data while OpenCart stays online does not, by itself, establish a zero-downtime launch.
8. Switch the domain and monitor the live store
When the destination passes your checks, complete the final data reconciliation and point the domain to the new installation. Verify HTTPS, redirects, checkout and incoming payment notifications on the actual live domain. Keep email-related DNS records intact if only the website is moving.
Remove the staging indexing restrictions from the public store. Check that search engines can reach the intended pages and that the sitemap uses live URLs.
Keep the old store as a protected reference during the agreed verification period. Define how you would reconcile orders taken by WooCommerce if a rollback became necessary. Simply pointing the domain back would not copy those orders into OpenCart.
What does an OpenCart migration cost?
The total depends on hosting, the chosen importer, paid editions or add-ons, storefront work, integrations and testing. The native product CSV importer can reduce tool costs for a catalog-only move, but preparing data and rebuilding the shop still require work.
Ask what a quote includes: historical orders, customer access, redirects, custom options, paid licenses, final synchronization and post-launch support. Compare equivalent scopes rather than a plugin price with a complete implementation.
Use the migrated catalog in Niwa
Once the WooCommerce catalog is ready, configure Niwa around your products and store policies. A customer looking for black work shoes in size 40 can ask about available options, compare the materials described in the catalog and choose a suitable product. On the website, supported cart actions let the customer add the selected item or variation to the cart and continue to checkout.
On WhatsApp, Niwa uses the product information and business rules to answer questions, help the customer choose the right size and complete the connected sale directly in the conversation. Check that the resulting order records the chosen model, size and quantity. Delivery, exchange and care answers should match the information maintained for the store.
For owner work, use the authorized WordPress assistant to request a stock update for a specific variation or revise a product description. Review the saved record, then check the customer-facing result. In the shoe example above, updating size 40 should change that variation's stock without changing size 41. That is why preserving options and stock relationships during migration matters to daily operations as well as checkout.
An existing WordPress store can install the standalone Niwa AI plugin. If you have already completed the move to WooCommerce, you do not need another website to use Niwa.
Frequently asked questions
Can I keep my domain?
Yes. A platform change does not require a new domain. Prepare the destination first and change the relevant hosting or DNS configuration at cutover. Page paths may still change and need redirects.
Will customers keep their old passwords?
That depends on the migration route and compatibility with your OpenCart installation. Confirm it before purchase and test an account. If the selected route cannot preserve login behavior, prepare a clear reset or activation process.
Can I copy the OpenCart design?
You can recreate its appearance in WordPress, but the OpenCart theme itself will not run there. Decide which layouts and functionality you need to retain.
Why are product images missing?
Check the source store URL, file permissions and image accessibility, then inspect the importer's log. For CSV imports, use direct image URLs and verify that galleries were imported, not only the first image.
Does migration automatically add an AI assistant?
Migration and assistant setup are separate tasks. A website built with AI uses AI during construction. An AI-powered store uses Niwa after launch for work such as answering catalog questions, helping customers choose products and assisting the owner with stock or content changes. Configure those tasks against the migrated data and test them on the new store.
Discuss your OpenCart migration with Niwa
Send your public store URL, OpenCart version and the features you need to keep. Include whether customer accounts and historical orders must move, along with the first task you want Niwa to handle in the new store, such as product questions or owner stock updates.
These details establish the data transfer, storefront work and AI adaptation your migration needs. Agree which integrations and third-party licenses are covered before implementation.
