SklepBaterie.pl – taking over and finishing a Magento 2 build with Hyvä
- Magento 2
- Hyvä
- Data migration
- B2C / B2B
- WF-Mag
- SEO
The project in figures
25 May 2026
Launch of the new store on Magento 2 with a Hyvä frontend.
around 181,000
Products in the migrated catalogue.
91%
Of existing URLs preserved through the migration.
around 40%
Fewer redundant or duplicated entries in the category structure.
Magento 2.4.7-p10
The platform version, with a Hyvä front end.
WF-Mag
The ERP integrated with the store.
B2B + B2C
Two sales models on one platform.
Project scope
Taking the project over from the previous supplier, an analysis of the inherited build, Magento 2 with Hyvä, data migration from CS Store, integrations, B2C and B2B sales, SEO, testing and launch.
Technologies
Magento 2.4.7-p10, Hyvä, OpenSearch, WF-Mag, Przelewy24, InPost, SMSAPI, Ceneo.
About the client
A store selling batteries and accessories to consumers and to businesses at the same time
SklepBaterie.pl sells batteries, rechargeable cells and power accessories — a range where the product is chosen for fitting a particular device rather than for its brand.
A catalogue like that is large by nature: one product exists in many variants of voltage, capacity and size, and a customer reaches it through parameters rather than a name. Hence around 181,000 items in the migrated catalogue, and what that asks of search and filtering.
Selling runs to consumers and to businesses in parallel, on the same platform and from the same catalogue, but on different commercial terms. That separation had to survive the migration along with the data.
Project context
- Industry
- Batteries, rechargeable cells and power accessories
- Sales models
- B2C and B2B on one platform
- Platform before the migration
- CS Store
- Target platform
- Magento 2.4.7-p10 with a Hyvä front end
The project had already started. First we had to establish what was genuinely ready to launch
In September 2025 Aurora Creation took over a Magento 2 build another supplier had started earlier. The store was to be moved from the CS Store platform to Magento 2.
Before the work could continue, the inherited code, configuration, environments and integrations had to be reviewed, along with the list of unfinished tasks. Only on that basis could we set the priorities that led to launch.
The project also involved a large product catalogue, a non-standard data structure, an ERP integration and both B2C and B2B sales. The migration had to account for continuity of sales and protect the organic visibility built up so far.
Project timeline
September 2025
Taking over the started build
The start of the analysis of the project left by the previous supplier, and the planning of the work needed to launch the new store.
25 May 2026
SklepBaterie.pl launches on Magento 2
The store goes live on Magento 2.4.7-p10 with a Hyvä frontend, after the migration, the integrations and the testing.
Five areas had to be brought to a state ready for launch
- 01
Taking the build over from the previous supplier
The project did not begin with a clean installation. The existing code, configuration, environments, integrations and open tasks had to be analysed, and then we had to establish which elements were essential before sales could start.
- 02
Migrating around 181,000 products with a non-standard data structure
The catalogue held products with rich attributes, different units of measure and conversion factors, among others from square metres to packs. On top of that, the standard exports from the previous system did not contain a complete and consistent set of data.
- 03
Connecting Magento 2 to WF-Mag and serving B2B customers
The integration had to account for stock levels, orders and contractors. Recognising business and individual customers, and pairing contractors by tax ID, was an important part of it too.
- 04
Hyvä and search across a large catalogue
The store's frontend was built on Hyvä. With a catalogue of this size the work also covered search, filtering, product listings and the solutions that follow from the nature of the range.
- 05
Migrating without losing the SEO structure built up so far
Changing platform meant putting the category structure in order while limiting the risk of losing organic traffic. 91% of existing URLs were preserved and the rest were covered by 301 redirects.
From an analysis of the inherited build to the launch of the new store
The work began by establishing the real state of the project and separating what was necessary for launch from features that could be built later. The team then focused on data migration, the key sales processes, the integrations, SEO and pre-launch testing.
Magento 2 store completion- 01
Analysis and takeover of the project
We reviewed the Magento configuration, the existing environments, the integrations, the data structure, the quality of the earlier work and the tasks that needed finishing.
- 02
Priorities and environments put in order
We agreed with the client the scope required to start selling. We set up new development and pre-production environments and put project communication in order. Features that did not block the start moved to a later stage.
- 03
Magento 2, Hyvä and OpenSearch
The store was built on Magento 2.4.7-p10 with a Hyvä frontend. OpenSearch was used for search and filtering across the extensive product catalogue.
- 04
Data migration from CS Store
We built a dedicated importer using data from CSV files and from reading the old platform's SQL database directly. The migration covered products, customers, orders, CMS content, blog posts and the category structure.
- 05
Integrations and B2B processes
Magento was connected to WF-Mag, Przelewy24, InPost, SMSAPI, Ceneo and OpenSearch, among others. We also built contractor pairing by tax ID, auto-completion of company data from the GUS business register, and a custom delivery method, „Transport busem sklepu” — delivery by the store's own van.
- 06
SEO, testing and launch preparation
We put the category structure in order and prepared 301 redirects, canonicals and the remaining elements of technical SEO described in the project. Before the start, an independent pre-production audit was carried out, along with tests of the imports, the cart, the checkout, payments, shipping, the ERP, B2B handling and the store's behaviour under load. The launch plan covered backups, switching the domain and the team's technical standby after the start.
Magento 2 connected to the ERP and the services that support sales
At the centre of the solution is Magento 2.4.7-p10 with a Hyvä frontend. The store was connected to an ERP system and to the services responsible for selected sales processes, payments, shipping, communication and search.
The data was moved into Magento 2 from the CS Store platform, and that is the only relation this page states a direction for. The scope of the remaining connections is what each system's role describes: the WF-Mag integration, delivered with the integratory.pl tool, covers stock levels, orders and contractors among other things, and the GUS register completes company data in the cart. „Transport busem sklepu” — delivery by the store's own van — is a shipping method built into the store rather than a separate system, which is why the figure does not draw it.
- CS StoreThe platform the data was moved into Magento 2 from
- WF-MagERP: stock levels, orders, contractors
- Przelewy24Payments integration
- InPostShipping
- SMSAPIIntegration with the SMSAPI service
- CeneoIntegration with Ceneo
- OpenSearchProduct search and filtering
- GUSCompany data auto-completion in the cart
Migrating around 181,000 products called for an import mechanism of our own
The standard exports from the previous platform did not give a complete and consistent picture of the data. The migration could not rest on an off-the-shelf export from CS Store alone.
Data from CS Store
- CSV files
- SQL database
Dedicated importer
Magento 2
The catalogue held rich attributes, different units of measure and specific conversion factors, among others from square metres to packs. A dedicated migration mechanism let us use data from more than one source instead of relying on the old platform's incomplete exports. The migration covered products, customers, orders, CMS content, blog posts and the category structure.
SEO migration
SEO migration – keeping 91% of the URLs, and 301 redirects for the rest
Changing platform is the moment when visibility built over years is easiest to lose. A catalogue this size means tens of thousands of addresses, and any of them may be in the index and in external links.
- URLs kept unchanged
- 91% of the existing addresses work on the new platform as they are. That is the cheapest protection there is: an address that needs no redirect loses nothing.
- Mapping the rest
- The remaining addresses were mapped by hand onto their counterparts in the new structure — not onto the home page or a parent category, because a redirect to something other than the expected content is a dead end for the user.
- 301 redirects
- The mapping shipped as 301s, that is, permanent. Search engines then move the signals to the new address rather than treating the change as temporary.
- Canonicals
- Canonical addresses point at one version of each view. In a catalogue with filtering and variants, that is the mechanism deciding what enters the index at all.
- Heading structure
- The headings on the category and product templates were put into one hierarchy, so every view has a single H1 and a readable division of its content.
- Tidying the categories
- The category structure had its redundant and duplicated entries removed. Fewer categories means fewer addresses competing for the same query.
- Watching visibility after the launch
- After going live the store was watched for indexing, crawl errors and the behaviour of the redirects. A migration ends not on launch day but when the data confirms the visibility held.
around 40%
reduction of the category structure
The number of categories was tidied by removing redundant or duplicated entries — around 40% fewer than in the structure inherited. The catalogue lost no route to a product in the process; what went were the routes leading to the same place.
The scope of the work involved in changing platform is described under migrating a store to Magento 2, and a build with a Hyvä front end in a fixed scope runs as a Magento 2 build with Hyvä.
Solutions that follow from how SklepBaterie.pl works
Non-standard units and conversion factors
The build accounts for products sold as pieces, packs or square metres, and for products that need unit conversion. Ceramic tiles are one example.
Pulse Deco Lux Siena tile — sold as a 1.08 m² pack, with the per-square-metre price conversion.
The tax ID entered in the invoice details is what later pairs the contractor in WF-Mag.
Pairing contractors by tax ID
The mechanism supports business customers and links contractor data between Magento and WF-Mag.
Company data auto-completed from the GUS register
The cart automatically completes company data from the GUS business register. It speeds up entering invoice details and reduces the risk of errors in contractor data.
„Transport busem sklepu” — the store's own van
A custom delivery method was built for a range that also includes larger and heavier products, or goods whose transport has to be arranged individually.
OpenSearch for a large product catalogue
OpenSearch was used to support product search and filtering across a catalogue of around 181,000 items.
URL structure and technical SEO after the migration
91% of existing URLs were preserved. 301 redirects were prepared for the rest. Canonicals on filters were added, and headings and title tags were optimised in line with the SEO guidelines.
On 25 May 2026 SklepBaterie.pl launched on Magento 2 with Hyvä
The project completed the stage of migrating sales from CS Store to Magento 2. The platform now serves a large product catalogue, B2C and B2B processes and the WF-Mag integration.
- 25.05.2026
- launch of the store on Magento 2.4.7-p10 with a Hyvä frontend
- around 181,000
- products in the migrated catalogue; customers, orders, CMS and the blog moved too
- 91%
- of existing URLs preserved through the change of platform
- around 40%
- fewer redundant or duplicated entries in the category structure
The remaining URLs were covered by 301 redirects. The category structure was put in order, and technical SEO covered canonicals on filters as well as headings and title tags.
Client testimonial
Zespół Aurora Creation przejął nasz projekt Magento 2 w trudnym momencie, gdy potrzebowaliśmy partnera, który realnie oceni sytuację i weźmie odpowiedzialność za dokończenie wdrożenia.See other references
This experience matters most in three kinds of project
- 01Magento 2 store completion
Taking over an unfinished Magento 2 build
When the project was started by another supplier and, before any further work, the inherited code, configuration, environments, integrations and the scope left before launch have to be assessed.
- 02Magento 2 migration
Migrating an existing store to Magento 2
When the change of platform covers a large catalogue, customer and order data, content and the category structure, and a standard export is not enough to carry the migration.
- 03B2B implementation on Magento 2
Magento 2 for B2C and B2B sales with an ERP integration
When one store has to serve both individual and business customers and work with an ERP system on processes such as orders, stock levels and contractors.
Frequent questions about the SklepBaterie.pl project
The scope of the takeover, the data migration, the integrations and preparing the store for launch.
The project was taken over in September 2025. The Magento 2 build had already been started by the previous supplier, so the first stage was an analysis of the existing code, configuration, environments, integrations and open tasks.
The store was moved from the CS Store platform to Magento 2.4.7-p10 with a Hyvä frontend.
The migration covered around 181,000 products, and also customers, orders, CMS content, blog posts and the category structure.
We built a dedicated importer that combined information from CSV files with reading the previous platform's SQL database directly. That let the import rest on more than one source of data.
The WF-Mag integration covered stock levels, orders and contractors among other things. Customer pairing by tax ID was built, along with auto-completion of company data from the GUS business register in the cart.
91% of existing URLs were preserved and the rest were covered by 301 redirects. The category structure was put in order, canonicals were added on filters, and headings and title tags were optimised in line with the SEO guidelines.
See other projects
Two projects that also started from a store as found: a new platform built after taking it over, and selling into many markets from one instance.
ImplementationPaxit: a new Magento 2 platform for B2B and B2C
An enquiry about care of the store as found, a diagnosis of its limits, and a new Magento 2 platform for a packaging manufacturer.
See the case study
ImplementationDiablo Chairs: one platform, many markets
A single Magento 2 instance serves three brands, 30 store views and 12 languages in cross‑border sales.
See the case study
Do you have a started Magento 2 build that needs bringing to launch?
Describe the stage the project is at, what has already been done and which parts need finishing or putting in order. On that basis we can establish the scope needed to take the project over and carry it on.
