Skip to main content
Digital strategy

Taking over an abandoned application: audit, cost, risks

Yes, an abandoned application can almost always be taken over, provided you start with an audit and check that you hold the rights to the code. Steps, risks and ballpark figures in DH.

Digi4··7 min read

Yes, an abandoned application can be taken over in the vast majority of cases, provided you start with an audit rather than with fixes. Expect an audit in the range of our diagnostic (12,000 to 30,000 DH excl. VAT), then maintenance of 1,000 to 20,000 DH excl. VAT per month depending on the size of the application.

Even before the audit, one question decides everything: do you own the source code? This article explains how to check, what the audit looks at, what a takeover costs and when it is better to rebuild.

Updated on 17 November 2026.

Why do applications end up abandoned?

The story is almost always the same: a freelance developer or a small agency delivers the application, then leaves, closes down or stops answering. Nobody in-house knows how it holds together. As long as nothing breaks, the issue waits. Then a certificate expires, a phone update breaks the mobile app, a server goes down, or a customer reports a security hole, and you have to act fast, with no documentation.

Do you really hold the rights to the source code?

This is the first check, before spending a single dirham on technical work. Having paid for an application does not automatically mean you own its code. Computer programs are protected in Morocco by Law No. 2-00 on copyright and related rights; in practice, what matters is what your contract says. What follows is general information, not legal advice: if in doubt, have the contract reviewed by a lawyer.

Gather and check:

  • The signed contract or quote: does it contain a clause assigning the rights to the code to the client, or only a right of use?
  • Invoices and proof of payment: many contracts only transfer the rights after full payment.
  • The code itself: do you have it, or only the live application? A Git repository in your name, an archive handed over at delivery?
  • Third-party components: a purchased theme, a licensed library, a vendor’s product. You can own your code without owning these building blocks.
  • The accounts: domain name, hosting, Apple and Google Play accounts, database. If they are in the provider’s name, recovering them goes through the provider.

If the contract only grants a right of use, or if the provider cannot be reached while the code is hosted with them, the takeover first becomes a contractual matter. We do not take over an application when the client cannot show they have the right to have it modified.

Our own rule is written down: custom development belongs to the client once paid, and we hand over code, database and access. Our products (Médiviz, Residapp) remain our property, under a right of use, and the data remains the client’s.

What does a takeover audit look at?

  1. Access: who holds what (servers, database, domain, app stores, email and payment services), and which passwords must be changed immediately.
  2. The code: is it complete, does it build, which language and framework versions, which dependencies are obsolete or vulnerable?
  3. Hosting: where the application runs, on what, with which backups, and have those backups ever actually been restored?
  4. The data: database structure, quality, personal data covered by Law 09-08.
  5. The risks: known vulnerabilities, secrets in the code, no tests, likely breaking points.

The deliverable is a short report: what works, what is dangerous, what to do and in which order, and a cost estimate. It is useful to you even if you hand the next stage to someone else.

How much does a takeover cost?

Stage (excl. VAT)RangeSource
Takeover auditIn the range of the diagnostic: 12,000 to 30,000 DHPublished rates (diagnostic), Digi4 estimate for the audit
Securing and stabilisingBased on the audit report, priced per day: team from 2,500 DH per day per profilePublished rates
Maintenance of a taken-over application1,000 to 20,000 DH per monthPublished rates
Rebuilding a module, if needed40,000 to 180,000 DHPublished rates

Assumptions: existing application in production, source code available. The low end of each range is a simple application (one role, few integrations), the high end a multi-role platform with a mobile app. Details on our pricing page. These are orders of magnitude, not quotes.

What are the risks of a takeover?

  • The recovered code is not the code that is running: the production version differs from the archive. The audit checks this before any change.
  • Dependencies that are too old: one update triggers ten more. The stabilisation cost can then exceed the initial estimate; the audit exists precisely to find this out beforehand.
  • Undocumented behaviour: business rules hidden in the code that nobody remembers. They are found by reading the code and talking to the users.
  • Access that cannot be recovered: an app store account or domain in the name of a third party who cannot be reached. This can force republishing under a new account.

We don’t promise that a takeover will be free of surprises. We promise that the surprises will be written in the audit report before you commit the budget for the next stage.

Take over or rebuild?

Taking over is almost always cheaper in the short term. Rebuilding becomes reasonable when several of these conditions are met:

  • the code is incomplete or you don’t hold the rights to it;
  • the technology is no longer maintained and upgrading amounts to rewriting everything;
  • the need has changed a lot since delivery;
  • every fix breaks something else, for lack of tests and structure.

In that case, the rebuild is done module by module, keeping the old application running during the transition and migrating the data. And sometimes the right answer is neither: if the application did what an off-the-shelf product does today, dropping it for a subscription is the cheapest option, and we will tell you so.

How does a takeover work at Digi4?

Four stages, described on our application takeover and maintenance page: audit, securing access, stabilisation, then fixed-fee maintenance. The online shop we delivered for Parahealth, a WooCommerce catalogue of several hundred products, ran for two to three years: at that scale, the structure of the catalogue and performance tuning decide what a takeover will cost later. For a broader management application, see also business platforms.

If your application handles invoices, our article e-invoicing in Morocco sets out what is actually required today.

Frequently asked questions

The previous developer refuses to hand over the code. What can we do?

First reread the contract: it sets out what must be handed over to you. If there is an assignment clause, it is a legal matter to handle with a lawyer. Technically, without the source code, the only option is to rebuild.

Can a mobile app that was removed from the stores be taken over?

Yes, if the code is available. It often has to be updated for Apple’s and Google’s latest requirements, then republished, ideally on a developer account in your name.

How long does the audit take?

A few days to two weeks depending on the size of the application, provided we have access. Recovering access is often what takes the longest.

Does the application have to be shut down during the takeover?

No, in most cases. The audit is done on a copy, and fixes go into production one at a time.

Describe your application and its situation: reply within 24 hours

Newsletter

Get our upcoming articles straight to your inbox.

Message a Digi4 manager on WhatsApp