Dolya & Co. LTD — Securing Communications, Empowering Critical Infrastructure

We led the full project over 6–8 months, with Dolya's internal team and project manager handling business operations and our team executing the entire technical migration end-to-end. The work split into five phases — four to launch in April 2025, and a fifth Hyvä migration phase now in active progress.

Phase 1 — Discovery, Schema Mapping & Architecture (November 2024 — December 2024)

This was the longest discovery phase of any migration we've shipped. There's no documented schema for a custom Evolution CMS implementation — every table, every field, every relationship had to be reverse-engineered before we could move a single product.

Key decisions resolved in this phase:

• Custom CMS → Magento 2 schema mapping — every Evolution CMS entity (products, categories, customers, content, vendor data, industry data) mapped to its Magento 2 equivalent, attribute by attribute

• B2B/B2C dual model — single Magento installation with customer-group-based logic for B2B/B2C segmentation, with shared catalog and differentiated pricing/portal access

• Customer groups — Guest, B2C Registered, B2B Customer, with custom pricing rules per group

• Industry & vendor taxonomy — 13 industries and the full vendor catalog mapped as Magento attribute structures so they could be filtered, navigated, and indexed for SEO

• URL preservation strategy — every Evolution CMS URL identified, mapped to the new Magento 2 URL, ready for 301 redirects

• What to migrate vs what to skip — products, customers, and content: yes. Order history: no (legacy system). Customer passwords: no (forced reset for security after cross-platform migration)

The architectural decisions in this phase determined how the rest of the project would run. No off-the-shelf migration tool was used — the migration was custom from line one.

Phase 2 — Magento 2.4.7 Build & Frontend Development (December 2024 — February 2025)

The new build was deployed to Hetzner Cloud VPS — chosen for cost-performance ratio, European data residency, and the bandwidth profile a 2,000-SKU multilingual store needs.

Core technical decisions:

• Magento 2.4.7 — current stable release at the time, full PHP 8.x compatibility, supported through Adobe's standard lifecycle

• Custom Luma-based theme — fully custom frontend development on Luma's component foundation, designed for both B2C product browsing and B2B procurement workflows

• OpenSearch for catalog search and faceted filtering across 2,000 SKUs with vendor, industry, frequency, and certification attributes

• PHP 8.x, MariaDB, Redis, Varnish standard production stack

Frontend development happened in parallel with the migration script work — the team designing the new UX, building component-level patterns for vendor pages, industry pages, and the B2B portal.

Phase 3 — Custom Migration Scripts & Data Move (February 2025 — March 2025)

This was the phase that turned the schema mapping from Phase 1 into running code. Custom migration scripts were written specifically for Dolya's Evolution CMS schema:

• Products — full migration of 2,000+ SKUs with attributes, categories, vendor associations, industry tags, and media

• Categories — hierarchical category tree rebuilt in Magento with original navigation preserved

• Customers — accounts migrated without passwords (forced reset on first login for security)

• Content (CMS pages, blog posts, vendor pages, industry pages) — migrated with content structure preserved for SEO

• Order history — not migrated (legacy system left behind for historical reference)

• URL mapping — ~3,000 301 redirects generated from Evolution CMS URLs to new Magento URLs, covering every product, category, content page, and vendor/industry landing page

Every migration script ran first on staging, with validation against production data before the next iteration. Edge cases (orphan attributes, malformed legacy data, missing references) were handled in script rather than left for post-launch cleanup.

Phase 4 — B2B Portal, Integrations & Launch (March 2025 — April 2025)

This phase built the platform Dolya actually needed — not just "Magento 2 with their data in it."

B2B-specific functionality:

• Custom B2B customer portal built from scratch — order history, saved product lists, recurring procurement support, account-level user roles

• Tier pricing — volume-based discounts for B2B customers

• Customer-specific pricing — negotiated prices visible only to the specific customer group / account

• B2B vs B2C catalog logic — same catalog visible to both, with differentiated pricing and portal features by login state

Vendor & industry navigation:

• Dedicated vendor pages (Motorola, plus other certified radio communication brands)

• Industry landing pages for all 13 verticals — each indexable for industry-specific search traffic ("rescue services radio", "mining communication systems", etc.)

CRM integration:

• Master CRM integrated for B2B lead routing, customer data sync, and the procurement pipeline that B2B operations depend on

Inventory management:

• Standard Magento inventory in production at launch; a custom Inventory Management module is in development now to handle Dolya's specific multi-source logic

Payment & delivery:

• Bank transfer as primary payment method (B2B/government contracts often require formal proforma billing rather than card payments)

• Nova Poshta integration for parcel delivery

• Ukrposhta integration for state-network delivery

• Own delivery option for enterprise/contract orders requiring direct logistics

Multilingual setup:

• Three languages — Ukrainian, Russian, English — with hreflang configured for correct cross-language SEO signals

SEO migration:

• ~3,000 301 redirects deployed at cutover

• Hreflang implementation across UA/RU/EN

• Schema.org markup — Product, Organization, BreadcrumbList

• Regenerated multilingual sitemap

• Metadata preserved or improved during migration

The cutover was effectively zero-downtime — DNS switch and the store was live on Magento 2.4.7 from one moment to the next. For a custom CMS migration of this complexity, that's a meaningful technical outcome.

Phase 5 — Hyvä Migration (In Progress)

Active right now. We're rebuilding the frontend on Hyvä Theme to push performance further as the catalog grows and traffic scales. Hyvä strips out the Luma frontend stack entirely, replacing it with a leaner Tailwind/AlpineJS architecture that delivers measurably better Core Web Vitals — particularly on mobile.

Preview environment is live at the staging URL while final implementation work continues.