Our store runs on Magento 1 and nobody supports it anymore
Adobe ended support for Magento 1 in 2020, so there are no security patches. We audit the store, move data and logic to Magento 2, and map old URLs so search rankings are not thrown away.
A large store on Magento 2, or a migration from Magento 1 that keeps your catalog and search rankings intact
We build stores on Magento Open Source and Adobe Commerce and migrate them from Magento 1. We prepare a quote after your brief.
Quote and schedule after your brief
Who it's for
- Stores with a large catalog, many filters and complex pricing rules
- Owners of Magento 1 sites that no longer receive security updates
- Businesses with several warehouses, currencies, languages or B2B price lists
- Companies that need deep integration with an ERP and a CRM
Problems we solve
The site slows down with a big catalog and many filters
We tune caching, the search engine (OpenSearch), indexing and queues. For the front end we use Hyvä or another lightweight theme when it fits your project.
Product and stock data sits in different systems
We connect your ERP, warehouse and PIM (a tool for managing product data) through APIs or scheduled imports. We agree which system is the master for prices, stock and orders.
We are afraid a migration will stop sales
We build the new version on a separate staging server first. The cutover happens at a quiet time you choose, and orders placed during the switch are imported separately.
What's included
- Audit of the current store: extensions, custom code, data, URLs, integrations
- Edition choice: Magento Open Source or Adobe Commerce (paid licence), with a cost comparison
- Catalog setup: product types, attributes, filters, multi-warehouse stock
- Design and front end: Hyvä or Luma theme, responsive on mobile
- Payments and shipping: Stripe, Adyen, PayPal, Klarna, plus carriers such as DHL, UPS or local post
- Data migration: products, customers, orders, reviews, 301 redirects
- Integrations with ERP, CRM, email tools and marketplaces
- SEO base: structured data, sitemap, canonical URLs, page speed
- Staging tests, production launch and post-launch support
- Handover of access, code repository and documentation to you
Choose the scope
Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.
01
Audit and plan
Owners of Magento 1 or a slow project, and teams still choosing a platform
- Review of code, extensions and database
- List of risks and what can move as is
- Recommendation: Magento or a simpler platform
- Work plan, estimate and timeline
02
Magento 2 store
New large stores and companies selling in several countries or languages
- Design and front end in your brand
- Catalog, filters, cart, payments, shipping
- Integration with one back-office system
- Basic SEO and analytics setup
- Training for your team
03
Migration 1→2 / Adobe Commerce
Stores on Magento 1 with many extensions and several integrations
- Data transfer and 301 redirects
- Replacing or rewriting outdated extensions
- Several integrations: ERP, CRM, warehouses, marketplaces
- Load testing and a rehearsal launch
- Post-launch support under contract
How we work
Brief and requirements
You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.
Pilot with a KPI
We agree on a measurable result on a small slice, such as migrating one category or hitting a target catalog page speed. Together we decide whether to continue.
Build on staging
We assemble the store on a test server. You can review pages before launch. Payment is made in stages.
Data migration and testing
We move products, customers and orders, then check redirects, payments and shipping. We run a rehearsal cutover.
Launch and handover
We switch the domain at the agreed time and hand over access, code and documentation. For the first month we watch for errors.
Scope and limits
- We do not promise that every Magento 1 extension will work on Magento 2. Some must be replaced or rewritten.
- We do not promise higher sales or rankings. We preserve what you have and remove technical blockers.
- We do not recommend Magento for a small store: hosting and maintenance cost more than on simpler platforms. If another option fits, we will say so in the audit.
FAQ
What is the difference between Magento Open Source and Adobe Commerce?
Open Source is free, but you pay for hosting and development yourself. Adobe Commerce has a paid licence and adds B2B features, segmentation and cloud hosting options. We price both in the audit.
How much does support cost after launch?
We prepare a quote after reviewing your brief. We list support and any third-party costs separately: subscriptions, APIs, hosting or media spend where the project needs them. Provider rates are checked before work starts.
Will we lose Google rankings after migration?
There is always some risk, and it can be reduced. We keep URLs or set 301 redirects, move meta tags and check the sitemap. Short-term ranking swings in the first weeks are possible and we cannot guarantee otherwise.
Who owns the code and accounts?
We agree on the handover of code, materials and account access before work starts. Third-party licences and services are listed separately when needed.
What do you need from us at the start?
Access to the current site and server, a product export, a list of integrations, brand materials and one decision-maker as a contact. Without these, the audit will be imprecise.
Can you handle multi-country stores?
Yes. We set up multiple languages, currencies and tax rules, payments through Stripe or Adyen, and international carriers. For the EU we check VAT handling and cookie consent with your accountant or lawyer.
Start with your task
Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.