Blog

The Migration Journey with eWings

How eWings migrates companies smoothly and securely from DynamicWeb 9 to DynamicWeb 10

Two completely different projects - one predictable and risk-free approach

More and more companies are switching to DynamicWeb 10. The reasons are clear: better performance, a future-proof architecture, new functionalities, and a version-less release system that drastically simplifies updates.

But alongside these advantages, there is often uncertainty:

  • What about existing custom code?
  • Will our ERP connection be affected?
  • How much downtime should we expect?
  • How complex is our current DW9 environment?

For many organizations, the biggest doubt is not about DynamicWeb 10 itself, but about the process of migrating to it.

Manufacturing company packing orders

eWings, a specialized DynamicWeb partner from Belgium, has developed an upgrade approach over the past few years that makes this process predictable, controlled, and surprisingly smooth - regardless of the size or technical situation of the existing DW9 installation.

In this case study, we explain the method using two different upgrade projects: Bluedrops and EMM. Two companies with completely different configurations, but the same result: a stable, efficient, and painless transition to DynamicWeb 10.

An approach focused on predictability and control

Step 1. The Blueprint - first understand what's there

Every upgrade project starts with a Blueprint - a complete analysis of the existing setup, including:

  • PIM & data structure
  • DAM & media management
  • eCom & language structure
  • integrations (such as Business Central or other ERPs)
  • DynamicWeb Swift and any customization

This analysis looks not only at the technical aspects, but also at daily use - like which fields are effectively managed, where do errors occur, which workflows could be more efficient?

This analysis determines which upgrade path is most suitable.

Step 2. Project structure and preparation

Based on the Blueprint, the project is set up in a project management tool.

  • clear roles and responsibilities
  • action points and dependencies
  • training moments
  • weekly follow-up structure

The goal: everyone knows what is happening and when.

Step 3. Choosing the right upgrade path

Not every DW9 environment requires the same process.

eWings typically works with two scenarios:

  1. Rebuild + migration (new DW10 environment)
    Suitable for outdated versions, complex custom code, old Swift themes, or PIM restructuring.

  2. Direct upgrade from DW9 to DW10
    Suitable when the existing environment is already close to the DynamicWeb standard.

In both cases, the live webshop remains operational throughout the entire preparation process.

Step 4. Test period with realistic scenarios

The test phase includes:

  • product enrichment
  • price and stock updates
  • ERP synchronizations
  • user rights and impersonation
  • navigation, filters, and language variants
  • ordering processes or catalog flows

All issues are centralized in the project management tool.

Errors are processed quickly, and everything is validated in advance, so that going live is not a surprise but a controlled transition.

Step 5. Going live as it should be - calm and manageable

Going live typically takes place on a Tuesday or Wednesday morning, where eWings:

  • closely coordinates with ERP partners
  • actively monitors during the first few days
  • responds quickly if something needs to be adjusted

For most customers, going live feels like “just continuing to work,” without downtime or disruption.

Step 6. Partnership after going live

An upgrade is not an end point.

DynamicWeb 10 opens new possibilities: improved workflows, faster management, new Swift version, etc.

eWings also supports customers after go-live to further optimize the platform and strengthen their eCommerce.

Two examples: one robust methodology

Case 1: Bluedrops: Complex DW9 → Rebuild to DW10 + migration

Bluedrops is a European wholesale distributor of swimming pool and wellness products, linking manufacturers with builders across regions like the Benelux, France, Scandinavia, and the DACH countries. The company offers a wide range of products including heating, chemicals, liners, covers, lighting, and innovative solutions like the Blueplus cleaning robot and Bluematic energy management system. 

Bluedrops was working on an older DW9 version with Swift 1.18, a lot of customization, and a PIM structure that was not optimally configured. The main challenges were:

  • multilingual product data
  • filters and attribute sets
  • outdated customization
  • mobile UX and page performance

eWings opted for a new DW10 environment, together with an upgrade to Swift 2.

The PIM was restructured and the team received training to ensure future-proof product management.

Result:

Faster site, improved UX, more stable ERP integration, and a live launch without interruption.

Manufacturing company packing orders

Case 2: EMM International BV: Recent DW9 → direct upgrade to DW10

EMM International BV is a Dutch-based company that develops, produces, and supplies products for the paint-processing industries, including automotive, aviation, marine, and industrial sectors. The company is known for its innovative, smart, safe, and sustainable solutions, and includes a wide range of products from personal protective gear to dust extraction systems and surface preparation tools. 

EMM merged with Finixa, resulting in a setup with four brands, 17 languages in PIM, and an extensive DAM structure. Despite this complexity, their DW9 environment was close to the standard, allowing for a direct upgrade.

eWings combined this with:

  • a multi-brand structure
  • centralization of PIM
  • preparations for SAP S/4HANA integration

Result:

A future-proof, all-in-one platform with clear governance and minimal impact during go-live.

Manufacturing company packing orders

What these projects demonstrate

Whether it's:

  • an outdated DW9 installation with a lot of customization,
  • or a recent setup with many languages, assets, and multiple brands...

the upgrade process can be surprisingly smooth when approached in the right way.

Both cases demonstrate:

  • a clear methodology
  • predictable timings
  • limited impact on daily operations
  • zero or minimal downtime
  • a stable, fast, and modern DW10 platform

An upgrade is not a mega-project; it is a process that can be perfectly planned and controlled.

Why DynamicWeb 10 is the logical next step

In addition to the benefits of the upgrade itself:

  • better performance
  • version-less releases
  • Swift 2 with greatly improved components
  • future-proof architecture
  • new AI capabilities

companies are primarily regaining control of their digital landscape: fewer systems, less maintenance, fewer risks.

Upgrade from DW9 to DW10

Looking to upgrade your own solution?

Upgrading software can feel like a challenge, but staying on outdated technology can be even more costly. DynamicWeb 10 represents a major leap forward, ensuring businesses are future-proof, secure, and efficient.

If you are curious to learn more about upgrading to DynamicWeb 10 - hit the link or get in touch.