Skip to content
095 430-06-28Consultation095 430-06-28

Moving a store from Magento to Horoshop

Store migration from Magento to Horoshop moves a large store from a heavy engine that needs separate hosting, developers and regular security updates to a platform where the technical side is included in the plan. Before the start we check the catalog and order volumes against Horoshop limits.

  • Magento configurable products become products with variants;
  • attributes and attribute sets turn into attributes and filters;
  • the category tree is recreated manually in the Horoshop admin panel;
  • the URL Rewrites section in Magento gives a complete list of addresses for 301 redirects;
  • we map customer groups and personal prices to Horoshop's B2B features;
  • we check the plan's product limit and the monthly order limit before work starts.

How a move from Magento to Horoshop works

Magento owners looking for store migration from Magento to Horoshop usually pay more for maintenance than the store needs: a separate server, developers and security updates. Before the switch we honestly compare your needs, because Horoshop has limits, and for large stores they are what decides whether the platform fits.

In Magento, products live in a model with attribute sets, and configurable products consist of simple child products. The built-in export in the Data Transfer section outputs products and customers as CSV. Addresses often have the .html suffix, and the URL Rewrites section contains the complete list of requests, so we build the redirect map without guesswork.

What we move from Magento and what we rebuild

  • products with SKUs, prices, stock and descriptions – by import from Excel after converting the CSV;
  • we rebuild configurable products as product variants with selection buttons;
  • we break attribute sets down into attributes that we build filters from;
  • we create the category tree manually in the Horoshop admin panel;
  • meta tags, canonical and category texts;
  • we build the design in the Horoshop editor and replace custom Magento modules with built-in features or external services.

We export customers and orders as spreadsheets to an archive. We compare customer groups and personal prices with Horoshop's B2B features: customer groups with their own prices, a personal price list and a wholesale client account.

How we work and what we need from you

  1. audit: catalog and order volume, custom modules, languages and separate stores;
  2. checking the number of products and orders against plan limits;
  3. an address map based on URL Rewrites;
  4. sections, import, filters, B2B settings if needed;
  5. test orders, domain switch, indexing monitoring.

We need access to the Magento admin panel or a database dump, a list of extensions and integrations, and access to Search Console and Analytics. The timeline depends on the catalog size, the number of language versions and custom modules; we name it after the audit.

Cost of migration from Magento and terms

We determine the cost after a free consultation and audit, because Magento stores vary in complexity. We fix the price and scope in the contract, the domain and the Horoshop admin panel belong to you, and the platform plan is paid separately. The stages are described on the page "Moving a store to the Horoshop platform", an SEO audit assesses the state of the website, and we discuss complex cases with integrations via the contacts page.

Questions and answers

Is Horoshop suitable for a large store coming from Magento?

It depends on the volume. Horoshop accepts up to 1,000 orders per month on any plan, and as many products as the chosen plan allows. If your numbers are higher, we will tell you during the audit before work starts.

What happens to languages and separate storefronts?

Horoshop fully indexes language versions, so we move product translations into the corresponding versions. We discuss separate Magento storefronts with different catalogs individually.

Will you move custom modules?

Module code does not move to Horoshop, because the platform is closed. For each module we look for a built-in equivalent, an external service or a JS snippet, and you get the list of these replacements during the audit.

How do we avoid losing traffic?

We take all addresses from URL Rewrites and Search Console, match them with the new ones and set up 301 redirects. After launch we check Search Console reports for crawl errors.