Zum Hauptinhalt springen

Migration

Migration to Tubach

Moving your shop is the biggest worry before a system switch. We take it off your shoulders, with a clear process, a test migration on real data and a cutover weekend that typically stays below two hours of downtime.

Which system are you coming from?

We've migrated from most common shop and ERP systems over the years. Plentymarkets is our specialty (19 years of Solutions experience). Other systems are handled individually, because every setup brings its own data and workflows.

System Status Typical timeframe
Shopware 5 Individual project possible 8 to 12 weeks
Shopware 6 Individual project possible 6 to 10 weeks
Shopify Individual project possible 6 to 10 weeks
WooCommerce Individual project possible 8 to 12 weeks
Plentymarkets Standard migration (Tubach specialty) 4 to 8 weeks
JTL On request individual
Magento On request individual
Custom build Individual project possible 8 to 12 weeks

What gets moved?

A migration is only clean if the important data moves over without loss. This matrix shows what we include in the standard package and what can be added in an extended migration.

Data object Standard Extended
Products including variants ✓ –
Images and media library ✓ –
Customer data ✓ –
Order history ✓ –
Invoices (archive) ✓ –
SEO URLs (301 redirects) ✓ –
Meta fields ✓ –
Reviews standard tools only individual
CMS content and magazine individual –

How does a migration run?

Every migration follows a clear six-step plan. You know at any time what is happening, what comes next and where we are.

  1. Kickoff and data analysis

    We look at your current system together, collect data volumes, edge cases and interfaces. The result is a concrete migration roadmap with responsibilities on both sides.

  2. Sandbox with real data

    We build a sandbox on a dedicated subdomain, populated with a current extract of your real data. That way you see early how your world looks in Tubach and can trigger adjustments before we go live.

  3. Test migration with validation

    A full dry run of the migration. We compare quantities, totals and samples against the old system and log every deviation. Only when the test migration is clean do we schedule the cutover.

  4. Training on site or remote

    Your team gets to know Tubach inside their own data. We train either on site or remotely across several sessions, depending on the size and complexity of your setup.

  5. Cutover weekend

    The actual move typically happens over a weekend. We import the final data state, activate the redirects and take your new system live. Downtime is typically below two hours.

  6. Hypercare over four weeks

    For four weeks after go-live we accompany you particularly closely. Short response times, daily check-ins if needed, fast adjustments. Only afterwards do we hand over to regular service operations.

What happens to your SEO?

Every old URL gets a 301 redirect to its new target. Existing rankings stay intact, provided that content and URLs are mapped cleanly. The new sitemap is generated automatically and submitted to Google Search Console. After the cutover we check the most important keywords and steer adjustments if Google sees something differently than expected.

What does it cost?

You find the one-off setup and migration costs in the setup block on the pricing page. The Start, Growth and Enterprise packages are described there with their typical scope, so you have a ballpark figure before we even talk.

To the pricing page

Switch without crashing.

Book a migration check. We spend 30 to 45 minutes with you in your current system and tell you honestly how a move to Tubach would look and what to pay particular attention to in your setup.

Book a migration check