When Replatforming in E-Commerce Makes Sense
Your current shop system has grown historically, can only be adapted with considerable effort, or is no longer suitable for new requirements.
Your system is reaching its limits when it comes to load, growth, internationalisation or new business models.
Your existing architectures and systems no longer sufficiently meet the new requirements for downtime prevention and stability.
Maintenance, adaptations and their releases tie up too many of your internal resources or cause disproportionately high costs.
Integrating your store system with adjacent systems now requires a great deal of effort, making it difficult to make changes to processes, which results in greater technical complexity during operation.
Why Companies Replatform with dotSource
You do not have to coordinate strategy, system evaluation, implementation and transition to operations across multiple service providers, but can set up the project as one seamless project.
If your target platform has not yet been decided, you will receive a technology-agnostic assessment of possible solutions. If required, we can also develop your e-commerce platform individually.
You get a replatforming solution that takes processes, integrations and adjacent systems into account and remains sustainable in operation.
You benefit from cross-industry project experience gained from complex digital initiatives in e-commerce and adjacent system landscapes, based on collaboration with more than 560 clients across different sectors and requirement profiles.
The Replatforming Process with dotSource
dotSource implements your replatforming in a multi-phase project. Depending on your system landscape and your requirements, the migration is carried out either as a cohesive project or as a gradual replacement of the existing system.
- Analysis of the existing shop, the system landscape as well as the functional and technical requirements
- Derivation of a suitable target architecture
- Selection of a suitable target system
- Definition of the implementation model: gradual or complete migration
- Definition of the migration strategy
- Specification and concept creation
- Requirements engineering
- Translation of the requirements into use cases, epics and work packages
- Business and technical preparation for implementation
- Migration of the new system respectively new version
- Creation and execution of test cases
- Automated tests
- CI/CD (Continuous Integration/Continuous Delivery)
- Security tests
- Ensuring fail-safe operation
- Go-live of the new shop system
- Hypercare for intensive stabilisation after go-live
- Ongoing support and further development, if desired
Replatforming with a Clearly Defined Timeline and Budget
To keep your replatforming project predictable, we structure the project into clearly defined phases. The effort involved, timeline and project scope are based on your existing system landscape, the migration scope and the target architecture you are aiming for.
Typical project timeline
- 1 to 3 months for architecture consulting and system selection
- 3 to 9 months for migration preparation and implementation
- up to 1 year for the overall project, including go-live, hypercare and transition to ongoing operations
Typical size for replatforming projects
Replatforming projects in the B2B context usually start at €100,000. Prices depend, among other things, on the system landscape and the integration effort involved. This is particularly the case when several systems are affected or established structures are to be replaced.
You can evaluate what your personal replatforming project could look like in a non-binding consultation appointment with us.
Book your free consultating session now
Your first step to a new E-commerce platform: Our non-binding consultation appointment
Your Contact for Further Questions
Our team will get back to you within one working day
- Our team will process your request as quickly as possible.
In the meantime, feel free to deepen your know-how in our replatforming knowledge base, with practical tips, current trends and proven success strategies.
Find More Details on Selected Replatforming Projects in Our Success Stories.
Companies Like Yours Trust dotSource With Their E-Commerce Projects
More on the topic of replatforming and migration in e-commerce
Further E-commerce services at a glance
Frequently Asked Questions About Replatforming
What does a typical replatforming process at dotSource look like?
dotSource implements replatforming as a multi-phase project. At the beginning, the specialist team analyses the existing shop, the system landscape and your requirements. On this basis, we work with you to define the target system and delivery model. This is followed by concept creation for the migration strategy and specification, which is then translated into use cases, epics and work packages. Our team then implements the replatforming technically, including testing, security checks and measures to ensure fail-safe operation. After the go-live, a hypercare phase follows before the project moves into support and further development if required.
Does dotSource also support you in selecting the target system?
Yes. If the target system has not yet been determined, dotSource will also be happy to support you with the system evaluation. To do this, our team gathers and structures your requirements. In addition, suitable target systems are assessed, including with the use of vendor demos. The selection is not made in isolation based on the functional scope, but in the context of your target architecture, integrations, your operating model and potential scalability.
Can you also have the replatforming implemented step by step?
Yes. The move to a new target architecture is carried out either as a single, end-to-end migration project or as a gradual replacement of the existing shop system. A step-by-step approach is particularly advisable if the system landscape has grown historically, if you want to reduce risks during ongoing operations, or if individual functions need to be migrated one after another.
How long does a replatforming project usually take?
Architecture consulting and system selection usually take between one and three months. Depending on the complexity of the project, you should allow around 3 to 9 months for migration preparation and implementation. Added to this are go-live, hypercare, and the transition to support and further development. Overall, a replatforming project can take up to 1 year or longer.
What costs should be expected for replatforming?
For B2B projects, an entry point from €100,000 is realistic. The actual costs depend primarily on the scope of the project, the number of affected systems, the integration effort and the target technical architecture.
Which systems does dotSource integrate as part of a replatforming project?
That depends on the specific project. Typically, replatforming affects not only the shop, but also adjacent systems such as ERP, PIM, CRM, CMS, OMS, marketing and BI systems, as well as other individual interfaces. The aim is not to set up your new commerce platform in isolation, but to transfer it into a resilient system landscape.
Does dotSource also carry out replatforming during ongoing operations?
Yes. Replatforming can be implemented in parallel with existing shop operations. This approach is particularly suitable for you if availability, the ability to place orders and ongoing business processes must be maintained during the migration. Whether a parallel approach makes sense depends on the system landscape, migration model and risk profile.
How does dotSource support you after go-live?
After go-live, a hypercare phase generally follows to stabilise the new system. During this phase, our team prioritises any issues that arise and fine-tunes processes to ensure a smooth transition to regular operation. Afterwards, the project can move into support and further development.
How does dotSource reduce risks during replatforming?
Our team reduces risks primarily through a structured approach. This includes an upstream analysis of the existing system and requirements, a robust target architecture, a clear migration strategy, specification and planning, as well as technical safeguards through test cases, automated tests, CI/CD, security tests and measures to ensure fail-safety. Depending on the project, a phased approach can also be chosen in order to further reduce risks during ongoing operations.
What experience does dotSource have with complex B2B and enterprise scenarios?
dotSource has been working across industries on complex digital projects in e-commerce and adjacent system landscapes since 2006. The agency has successfully delivered more than 700 digital projects for over 560 clients. These include, in particular, projects involving evolved architectures, multiple connected systems, international requirements and complex B2B processes.
How does dotSource support international replatforming projects?
For international replatforming projects, our team uses, for example, an already well-functioning country shop as a blueprint for further rollouts. For international projects, scalability, the reusability of functions, integrations into central systems, as well as alignment with country-specific requirements are particularly crucial.
What happens to ERP, PIM or CRM systems during replatforming?
Your existing systems are not simply replaced as part of replatforming; instead, they are assessed in the context of the target architecture. Depending on the initial situation, they remain connected, are technically adapted or are reintegrated in interaction with the new shop system. The aim is to ensure that processes and data flows function consistently after the system change and that your shop is not operated as an isolated standalone solution.