← All projectsArchitecture case study

ToolMart

Moved an Australian tools retailer from Magento 1 to Adobe Commerce On-Premise: full data migration, rebuilt themes and product page, and new quoting and catalogue-request features across multiple custom modules.

From Magento 1 to Adobe CommerceA full data migration with the business logic carried across.
Integration map

From Adobe Commerce On-Premise out to 10 systems

The platform at the top and the integrations that hang off it. Covers platforms, extensions and delivery.

Highlights

Four things that set this build apart

  • Magento 1 → Adobe Commerce

    Migration architecture and full data migration, designed and led.

  • Product page rebuilt

    Brand, labels, shipping data, stock ETA and warranty, end-to-end.

  • Quotes & catalogues

    Request-a-Quote and Request-a-Catalogue, each with its own entity and grid.

  • Five extensions tailored

    Purchased extensions extended to match site behaviour.

Architecture overview

A rebuilt platform with the business logic carried over

The storefront and support tools were rebuilt on Adobe Commerce, with purchased extensions extended rather than replaced.

Scroll sideways to explore the diagram

ChannelsPlatformBusiness systemsStorefrontSupport staffAdobe CommerceOn-Premise · custom modulesRebuilt product pageRequest-a-QuoteRequest-a-CatalogueAdmin IP loggingExtended add-onsMirasvit Search UltimatesearchTrustpilot ReviewsreviewsXtento PDFdocumentsAmasty · WeltPixelbanners & carouselsCustomers & support staffMultiple custom modules5 purchased extensions
What makes it different

Themes and extensions were rebuilt on the new architecture rather than dropped, so the store’s existing business logic survived the move.

What the platform does

What the platform does

  • Migration

    Magento 1 to Adobe Commerce On-Premise, including full data migration.

  • Themes & extensions

    Custom themes rebuilt and extensions redeveloped on the new architecture.

  • Product page

    Rebuilt end-to-end: brand display, extra info, custom labels, shipping data, stock ETA and warranty.

  • Quotes & catalogues

    Request-a-Quote and Request-a-Catalogue, each with its own entity, admin grid and e-mail notifications.

  • Extension tailoring

    Mirasvit instant-search provider, Amasty banner active-date validation, WeltPixel Owl Carousel product block, Trustpilot review invitations on order save and Xtento order-PDF data, all adapted to the site.

  • Pricing hygiene

    A scheduled job clears expired special-price windows, and Call for Price products hide Add to Cart.

  • Checkout & cart

    Billing address moved to the top of checkout, the shipping method shown on the thank-you page, and cart line names built from custom attributes.

  • Support tools

    An admin IP-logging page and extra order-view tooling for support staff.

  • Performance

    An auth-popup block removed sitewide for faster page loads.

  • Delivery

    Git workflow, code reviews and deployments through migration and post-launch stabilisation.

How the migration ran

Plan, move, rebuild, stabilise

From an ageing Magento 1 store to a stable Adobe Commerce platform.

  1. Step 1

    Plan

    Designed the migration architecture from Magento 1 to Adobe Commerce On-Premise.

  2. Step 2

    Move

    Full data migration to the new platform.

  3. Step 3

    Rebuild

    Themes and extensions redeveloped, preserving existing business logic.

  4. Step 4

    Stabilise

    Git workflow, reviews, deployments and performance fixes after launch.

Key technical challenges

Moving without losing anything

An old platform, a crowded extension stack and features the business relied on.

  1. A legacy platform

    An ageing Magento 1 store with business logic spread across third-party extensions.

    Solution

    Migration architecture, full data migration, and themes and extensions redeveloped on Adobe Commerce.

    Result

    Existing business logic carried over to the new platform.

  2. A richer product page

    Product pages had to show brand, labels, shipping data, stock ETA and warranty.

    Solution

    Rebuilt the product detail page end-to-end.

  3. Requests, not just orders

    Some customers ask for a quote or a catalogue rather than checking out.

    Solution

    Separate Request-a-Quote and Request-a-Catalogue features, each with its own entity, admin grid and e-mails.

  4. Slow pages

    A sitewide auth-popup block slowed page loads.

    Solution

    Removed it sitewide after migration.

    Result

    Faster page loads.

  5. Stale prices

    Expired special-price windows lingered on products.

    Solution

    A scheduled job clears them automatically.

    Result

    Pricing stays accurate without manual admin cleanup.

The migration pathData, themes and logic moved to the new platform.
Magento 1DatamigrationAdobeCommerce
How a quote request travelsEach request type has its own entity, grid and e-mails.
CustomerrequestQuoteentityAdmingridE-mail
Technologies and integrations

The stack behind it

Platforms
Magento 1Adobe Commerce On-PremisePHPMySQL
Extensions
Amasty Banner SliderMirasvit Search UltimateWeltPixel Owl CarouselTrustpilot ReviewsXtento PDF
Delivery
GitCode reviewDeployments
Skills shown
Migration architectureData migrationTheme developmentRelease management
Full build log

The work, piece by piece

  1. Designed and led the migration architecture from Magento 1 to Adobe Commerce On-Premise, including full data migration.

  2. Rebuilt custom themes and redeveloped extensions on the new architecture, preserving existing business logic.

  3. Rebuilt the product page end-to-end: brand display, extra info, custom labels, shipping data, stock ETA and warranty.

  4. Request-a-Quote and Request-a-Catalogue features, each with its own entity, admin grid and e-mail notifications.

  5. Extended Amasty Banner Slider, Mirasvit Search Ultimate, WeltPixel Owl Carousel, Trustpilot Reviews and Xtento PDF for site-specific behaviour.

  6. Admin IP-logging page and extra order-view tooling for support staff.

  7. Managed Git workflow, code reviews and deployments through migration and post-launch stabilisation.

  8. Post-migration performance work, including removing a sitewide auth-popup block for faster page loads.

More case studies

Related platforms I've built

USA06
B2B catalog

Sterling Machinery

  • MigratedCustom PHP → Magento 1 → Magento 2
  • BuiltFive lead pipelines for buy, sell and wanted requests
  • IntegratedAuction feeds through the Web API
9custom product data entities
Beirut, Lebanon03
ERP integration

Antoine Online

  • IntegratedTwo-way ERP sync on cron, with a run log in the admin
  • BuiltArabic product URLs through a custom router
  • FixedBack-orders at the root, in the CSV import
6data types in the two-way ERP sync
Kuwait07
Fashion & beauty

Minamin

  • IntegratedERP sync split into cron and a RabbitMQ queue
  • BuiltBanner & product-label admin from scratch
  • DesignedTwo branded themes, 203 style files over the base
2storefronts
Available immediately

Facing a similar problem? Let's talk.

I am available immediately for senior Adobe Commerce roles and contract work. Tell me what you are building.