At ECASTE, we don't only build applications from a blank page. A significant part of our work consists of taking over existing projects: software built by a previous provider, a freelancer who has moved on, or an in-house team that no longer exists, and on which the business depends every day. After the Reducbox platform a few years ago, then more recently upmates, we have just signed a new takeover contract with DPA-Europe.
DPA-Europe, France's leading Apple refurbisher
DPA-Europe, known to consumers under the Reborn brand, is the French leader in refurbishing Apple phones. iPhones of course, but also Macs, iPads and AirPods: every device entering their workshops is diagnosed, repaired, tested, graded and put back on the market. A demanding industrial activity, with high volumes and strict traceability requirements.
To run this activity, DPA-Europe relies on custom-built business software based on the PHP framework Laravel. Device flows, diagnostics, grades, stock, sales: it is the backbone of the company. And as is often the case with business tools, it is not software you can stop, replace or rewrite overnight.
DPA-Europe has just entrusted ECASTE with the mission of maintaining and evolving this software. A real challenge: the takeover is happening without any technical documentation.
Taking over a project without documentation: a discipline of its own
Taking over someone else's code is very different from developing your own project. You have to understand architectural choices you didn't make, conventions that are sometimes implicit, business rules hard-coded in unexpected places. Without documentation, every feature must be rediscovered, every dependency checked, every server configuration tracked down.
This is precisely where an experienced provider makes the difference. A poorly executed takeover risks breaking a critical feature while trying to fix another, losing data, or bringing production to a halt. A well-executed takeover, on the contrary, secures a software asset the whole company depends on, and puts it back on a path of evolution.
Our takeover method, step by step
Over successive takeovers (Reducbox, upmates, and now DPA-Europe), we have formalized an approach designed to be methodical and free of surprises for the client:
- Retrieving and securing the source code: the first step is to bring the entire source code, scripts and configurations into our secure GitLab. The code is versioned, backed up and accessible only to authorized people. Nothing depends on a single server or workstation anymore.
- Reverse engineering: without documentation, we rebuild the map of the software from the code itself. Data models, routes, controllers, scheduled tasks, external integrations, asynchronous jobs: we document what we discover as we go, so that the knowledge is never again locked in a single head.
- Deployment on our test infrastructure: we redeploy the complete project on our own infrastructure, with a test database, to verify that we master the whole chain — from installing dependencies to going live. It is the best possible test of our understanding of the project.
- Switching pre-production and production: once the project is under control, we switch the pre-production and then production servers to our GitLab infrastructure, with automated, reproducible deployments. Every release becomes traceable, testable and reversible.
Only once these steps are complete does the evolution phase truly begin: bug fixes, new features, optimizations. On a foundation that is finally documented, with a reliable delivery process.
What our previous takeovers taught us
Taking over Reducbox, a discount voucher platform, taught us the importance of securing first and evolving second. The upmates takeover confirmed that an honest code audit, presented to the client without jargon, is worth more than a complete rewrite promised too quickly. In both cases, the key was the same: break nothing that works, while preparing the ground for what needs to change.
"Taking over a project means accepting to inherit other people's choices. Our role is not to judge the existing code, but to understand it, secure it and give it a future. On business software like DPA-Europe's, service continuity comes first." — Emmanuel Castellani, founder of ECASTE
Why entrust the takeover of your software to ECASTE
For more than 16 years, ECASTE has been developing and maintaining web and mobile applications for companies of all sizes, in the Alpes-Maritimes and beyond. We master the technologies most often found in existing business software: PHP and Laravel, Vue.js, Node.js, as well as native iOS and Android. Above all, we know that software only has value if it keeps running.
- A secure GitLab infrastructure and automated deployments
- Documentation rebuilt during the takeover and handed over to the client
- A single, available point of contact, based in Nice
- A progressive approach: secure, understand, then evolve
Conclusion
The takeover of DPA-Europe's business software illustrates what has become an essential part of our work: giving a future to existing software that is often critical and sometimes orphaned. Reverse engineering, securing the source code, redeployment, switching servers: each step is carried out with the same rigor as if we had written the code ourselves.
Is your provider no longer available? Is your business software no longer maintained? Contact us: we will study your project and propose a clear takeover plan, without jargon and without surprises.