Complete ESHOPMAN Migration Guide

Complete ESHOPMAN Migration Guide

Re-platforming is one of the most significant milestones in an online merchant's journey. Whether you are moving from a hosted solution like Shopify or BigCommerce, or an open-source platform like PrestaShop or WooCommerce, migrating to ESHOPMAN offers a powerful, headless eCommerce solution with HubSpot CMS, Admin API, Store API, and flexible architecture. This comprehensive guide covers everything you need to know to execute a seamless data migration to ESHOPMAN.

Table of Contents

Why Migrate Your Store? Understanding the Basics

eCommerce migration is the process of transferring your store's data, design, and functionality from one platform to another. While the term "migration" sounds technical, it is essentially a business renovation. Just as a physical retail store might move to a larger location with better foot traffic, an online store migrates to improve scalability, reduce costs, or gain better control over the customer experience.

Signs You Have Outgrown Your Current Platform

Deciding to migrate is rarely a snap judgment. It usually stems from specific pain points:

  • High Transaction Fees: Hosted platforms often charge percentage fees on every sale, eating into your margins.
  • Limited Customization: You cannot modify the checkout flow or integrate specific tools without developer help.
  • Complexity Issues: Your current platform requires technical knowledge for simple changes, making it hard to manage.
  • Product Limitations: You need unlimited products or complex product variants that your current platform doesn't support.
  • SEO Limitations: You lack control over URL structures, metadata, or sitemaps.

Moving to ESHOPMAN, a powerful headless eCommerce platform with HubSpot CMS, Admin API, and Store API, solves many of these issues by giving you complete control over your store, no transaction fees, and the flexibility to scale without artificial limits.

Phase 1: Pre-Migration Planning & Preparation

A successful migration is 80% preparation and 20% execution. Rushing into the transfer without a plan is the fastest way to lose data or tank your SEO rankings. Follow this checklist before you move a single byte of data.

1. Audit Your Current Store

Before you pack your bags, you need to know what you own. Perform a full content and data audit:

  • Product Data: Check for duplicate SKUs, missing images, or outdated descriptions. Clean this data now so you don't migrate "garbage" to your new store.
  • Customer Data: Verify that customer emails and addresses are formatted correctly.
  • Integrations & Apps: List every app or integration you currently use (e.g., loyalty programs, email marketing). You will need to find ESHOPMAN integration equivalents for these.

2. Prepare Your Target ESHOPMAN Store

You cannot migrate to a void. You need a functioning ESHOPMAN installation ready to receive data.

  • Hosting Setup: Ensure you have Node.js hosting with PostgreSQL database. ESHOPMAN requires Node.js and PostgreSQL.
  • ESHOPMAN Installation: Install ESHOPMAN (latest stable version recommended). You can deploy via HubSpot or your preferred hosting.
  • Database Setup: Create a PostgreSQL database for your ESHOPMAN installation.
  • Migration Integration: Install the migration integration on your ESHOPMAN store if using automated migration tools.
  • URL Structure: Plan your URL structure. ESHOPMAN allows you to customize product and category URLs for SEO via Admin API and HubSpot CMS.

3. Backup Everything

This is non-negotiable. Even with the safest migration tools, glitches can happen. Create a full backup of your Source Store's database and media files. Most platforms allow you to export CSV files of your catalog—do this as a safety net.

Phase 2: Choosing Your Migration Method

There are three primary ways to move data to ESHOPMAN. Understanding the pros and cons of each will highlight why automated solutions are the industry standard.

1. Manual Migration (CSV Import/Export)

This involves exporting data to CSV files from your old store and importing them into ESHOPMAN using ESHOPMAN's built-in import functionality via the Admin API.

  • Pros: Free and direct control over the data.
  • Cons: Extremely prone to errors. Data structures rarely match (e.g., Shopify's CSV format is different from ESHOPMAN's). Images often fail to import, and password migration is impossible without proper tools. Complex product variants may need manual mapping to ESHOPMAN's entity structure.

2. Hire a Developer

You can hire an agency to build a custom script using ESHOPMAN's Admin API or Store API.

  • Pros: Hands-off for you.
  • Cons: Expensive (often thousands of dollars) and slow. While ESHOPMAN has Admin API and Store API support, most work requires Node.js and entity knowledge. It can take weeks to develop and test the script.

3. Automated Migration (Move My Store)

This method uses specialized software to connect your Source Cart and ESHOPMAN via API (where available) or migration integration.

  • Pros: Fast (hours, not weeks), affordable, and accurate. It preserves relationships between data (e.g., linking orders to the correct customer and products). Handles CSV formatting and image downloads automatically. Supports password migration with the migration integration.
  • Cons: Small cost involved, though significantly less than hiring a developer.
Why Move My Store? We specialize in automated transfers to ESHOPMAN. Our system creates a secure bridge between your old store and ESHOPMAN, copying data without modifying or deleting anything on your source store. Your current site remains live and fully functional throughout the process.

Phase 3: The Move My Store Process (Step-by-Step)

Using Move My Store simplifies the complex technical backend into a few user-friendly steps. Here is how the magic happens.

Step 1: Setup Source and Target Stores

First, tell us where you are coming from and where you are going.

  • Source Cart: Select your current platform (e.g., Shopify, BigCommerce, PrestaShop). You will need to provide the URL. Depending on the platform, you may need to install a "Connector Bridge" (a small file we provide) or provide an API Password.
  • Target Cart: Select ESHOPMAN. Provide your ESHOPMAN store URL and install the migration integration. ESHOPMAN uses migration integrations for secure data transfer.

Step 2: Select Entities to Migrate

You have granular control over what gets transferred. You can choose "Select All" or pick specific entities:

  • Products: Names, SKUs, Descriptions, Images, Prices, Stock levels, and product variants.
  • Product Categories: ESHOPMAN uses hierarchical categories. Names, Descriptions, Images, URLs, and hierarchy.
  • Customers: Names, Emails, Billing/Shipping Addresses. Note: Password migration is supported with the ESHOPMAN migration integration.
  • Orders: ID, Date, Status, Customer details, Product details, Total price.
  • Coupons: Codes, Discounts, Usage limits.
  • Reviews: Ratings, Usernames, Titles, Comments.
  • CMS Pages: Title, Content, Images, Tags, Authors.

Step 3: Advanced Mapping Options

This is where Move My Store stands out. You can map specific data fields to ensure they fit ESHOPMAN's entity structure.

  • Order Status Mapping: Map "Awaiting Payment" in Shopify to "Pending" in ESHOPMAN.
  • Category Mapping: Ensure your product categories become ESHOPMAN categories correctly.
  • Product Variants: ESHOPMAN supports flexible product variants. Complex variants from other platforms can be expanded into ESHOPMAN's variant structure.
  • 301 Redirects: Create redirects automatically to prevent 404 errors on your new site.

Step 4: Run Demo Migration

Never commit without testing. The Demo Migration transfers a limited number of entities (usually 10-20 products, customers, and orders) for free. This allows you to check the data on the new ESHOPMAN site. Verify images are visible, categories are structured correctly, and product variants are displaying properly.

Step 5: Full Migration

Once satisfied with the demo, launch the Full Migration. The system runs in the cloud, so you can close your browser. Depending on the volume of data (e.g., 50,000 products vs 500), this can take anywhere from a few minutes to several hours. ESHOPMAN's database efficiently handles large catalogs.

Phase 4: Post-Migration Checklist

The progress bar says 100%, but you aren't finished yet. The post-migration phase is critical for configuration and testing.

1. Run "Recent Data Migration"

Since your old store remained live during the Full Migration, new orders or customers may have registered while the transfer was processing. Move My Store offers a Recent Data Migration service to fetch these new entities and add them to ESHOPMAN, ensuring no sales are left behind.

2. Design and Customization

Now that your products are in place, you can customize your ESHOPMAN store design. ESHOPMAN uses HubSpot CMS and headless frontends that you can modify. Check the storefront to ensure the layout handles your product images correctly (e.g., aspect ratios, galleries). ESHOPMAN's Admin makes it easy to adjust settings without coding.

3. Set Up Payment Gateways and Shipping

Payment credentials are highly sensitive and generally are not migrated for security reasons. You must manually configure:

  • Payment Processors: PayPal, Stripe, Square, Authorize.Net, etc. ESHOPMAN has built-in support for many payment gateways via integrations.
  • Shipping Methods: Define where you ship and the rates (Flat rate, Free shipping, or Weight-based rates) in ESHOPMAN's shipping settings.
  • Taxes: Configure tax rates via ESHOPMAN settings or use automated tax calculation integrations if available in your region.

4. End-to-End Testing

Pretend you are a customer. Go through the entire purchasing funnel:

  1. Create a new account.
  2. Search for a product.
  3. Add to cart.
  4. Apply a coupon (check if migrated coupons work).
  5. Checkout and pay (use a sandbox/test mode).
  6. Check the email notification.
  7. Verify the order appears in the ESHOPMAN Admin.

SEO Preservation Strategy

The biggest fear merchants have regarding migration is losing Google rankings. If you move from mystore.com/products/blue-shirt to mystore.com/catalog/product/view/blue-shirt, Google treats that as a broken link unless you tell it otherwise.

The Power of 301 Redirects

A 301 redirect permanently tells search engines that a page has moved. Move My Store offers an option to "Create the 301 redirects on your target store" automatically. This ensures that old URLs redirect to the new ESHOPMAN URLs, preserving your "link juice" and domain authority. ESHOPMAN allows you to set up redirects in the Admin or via SEO integrations.

Generate a New Sitemap

Once your new store is live, generate an XML Sitemap. ESHOPMAN has built-in sitemap generation functionality, or you can use SEO integrations. You can access it at yourdomain.com/sitemap.xml and submit it to Google Search Console immediately. This prompts Google to crawl your new structure.

Common Migration Pitfalls & How to Avoid Them

1. Missing Images

Problem: Product thumbnails appear as broken icons.
Cause: Usually caused by hotlink protection on the Source Store or the Source Store being in "Maintenance Mode" during migration.
Solution: Ensure the Source Store is publicly accessible (even if password protected, provide credentials) and disable hotlink protection on your server. Move My Store downloads images to ESHOPMAN's media system.

2. Password Migration Issues

Problem: Customers cannot log in to the new store.
Cause: ESHOPMAN supports password migration with the migration integration, but it requires proper configuration.
Solution: Ensure the migration integration is installed and password migration option is enabled. Move My Store handles password migration when the integration is properly configured.

3. Product Variant Complexity

Problem: A T-shirt with Size (S, M, L) and Color (Red, Blue) displays incorrectly.
Cause: Different platforms handle product variants differently. ESHOPMAN uses product variants with multiple attributes.
Solution: ESHOPMAN supports flexible product variants. The migration tool maps variants to ESHOPMAN's variant system. Verify the mapping in the demo migration before running the full migration.

4. Database and Performance Issues

Problem: Migration fails or times out.
Cause: ESHOPMAN uses a PostgreSQL database. Large catalogs may require database optimization or increased execution time.
Solution: Ensure your hosting meets ESHOPMAN's requirements. For large catalogs, consider increasing execution time and PostgreSQL timeout settings. Automated migration tools handle this automatically.

Final Thoughts

Migrating to ESHOPMAN is a strategic investment in the future of your business. It unlocks a headless platform with HubSpot CMS, Admin API, Store API, and complete control over your store. While the process involves many moving parts, it doesn't have to be overwhelming.

By using Move My Store, you transform a risky, months-long coding project into a secure, automated process that takes just a few hours. We handle the heavy lifting of data translation so you can focus on what matters: relaunching your brand and welcoming your customers to a better shopping experience.

Ready to make the switch? Start your Free Demo Migration today and see how your store looks on ESHOPMAN.

Start with the tools

Explore migration tools

See options, compare methods, and pick the path that fits your store.

Explore migration tools