Shoptet → Shopify
Classic migration for companies that have outgrown Shoptet's capabilities. Products, variants, customers, historical orders, reviews, blog.
Service — E-shop migrations
E-shop migrations between platforms without data loss
Software-driven migration of products, customers and orders between platforms like Shoptet, Shopify, WooCommerce or custom solutions. Minimal downtime, no lost historical orders.
Discuss migration →An e-shop migration is a project with high error risk and high cost of mistakes. Lost historical orders, broken redirects, mis-mapped product variants — typical bugs you then chase for months. We do it the software way: scripts, validations, repeated runs on staging until everything matches at 100%.
When migration makes sense
Typical situations our clients arrive with.
WooCommerce → Shoptet
Other direction — from self-hosted WooCommerce to managed Shoptet. Often after acquisition or when a company doesn't want to maintain infrastructure.
Custom → modern platform
An e-shop built years ago on a custom framework. Migration to Shopify or Shoptet simplifies maintenance and team.
Merging two e-shops after acquisition
Two companies, two databases, one new brand. Mapping overlaps, customer deduplication, decisions on duplicate SKUs.
Multi-language migration
From a single-language e-shop to multilingual. Translation mapping, hreflang setup, currency handling, regional legal documents.
Prestashop / OpenCart end-of-life
The platform is no longer maintained. Migrate to a live system before it becomes a security risk.
How a migration runs
Standard flow from audit to cutover.
Source data audit
We map everything in the old e-shop. Often we find data the company forgot about (custom fields, redirects, B2B access).
Mapping + scripts
Field-by-field mapping. Scripts are written idempotent so we can re-run until output matches.
Staging migration
Full run on a clone of the new e-shop. You review the data manually, approve, and we fix any findings.
Production cutover
Planned hour, transfer, smoke tests, DNS cutover. Usually overnight for peace of mind.
What we work with
Standard e-commerce stack and our own ETL tooling.
Platforms
- Shoptet
- Shopify
- WooCommerce
- Magento, Prestashop
Custom DBs
- MySQL / MariaDB
- PostgreSQL
- SQL Server
ETL scripts
- Python
- TypeScript
- custom pipelines
Validation
- data integrity checks
- row counts, checksums
- byte-for-byte diff
SEO redirects
- 301 maps
- nginx / Apache rewrites
- application redirects
What else we migrate
- reviews
- blog and articles
- custom fields
- B2B access
Frequently asked questions
What clients ask before we start a migration.
How much does migration cost and how long does it take?
A typical mid-size e-shop takes 3–6 weeks; price depends on data volume and custom logic.
A pre-project audit always comes first to give a realistic estimate. The audit itself costs a fraction of the migration.
What about downtime during migration?
We aim for zero downtime through orchestrated cutover. Worst case 1–2 hours during off-peak night hours.
What about historical orders?
They migrate. The key is to have the customer's complete history in the new system — that's the reason customers stay with you.
Do you also handle SEO redirects?
Yes. The map of old URLs to new URLs is a standard part of migration. Without it you'd lose search rankings built up over years.
What if the old system has a custom field Shopify can't handle?
We use metafields, custom apps, or rework the structure. Before migration we map all custom fields and propose a path.
Do you guarantee nothing gets lost?
We audit data before and after migration with byte-for-byte comparison of critical objects (orders, invoices, customers). If anything doesn't match, we don't cut over.
Let's work together
Describe your situation or request and we typically reply within one business day.
- info@hruby.software
- +420 211 221 865
- Navrátilova 666/7, Prague 1