All posts
Product

How a Netherlands Company Can Move an Existing Mobile App to an Offshore Team Without a Rebuild

Published on 18 Nov 2026

how-a-netherlands-company-can-move-an-existing-mobile-app-to-an-offshore-team-without-a-rebuild

A Dutch company can hand a live iOS, Android or cross-platform app to an offshore team without rewriting it, as long as the move is run as a knowledge transfer rather than a code transfer. The sequence that works has five steps. Audit the codebase and release pipeline. Embed one senior engineer in your existing repositories against a live sprint. Let the offshore team prepare a release while the incumbent watches. Then reverse the roles until the offshore team ships a store release on its own. Then scale.

724SOFTWARE, a Vietnam software team whose mobile work includes in-app stock trading built into an operating mobile banking app (MyVIB), starts with one senior engineer validated against a live sprint and then scales, so the app stays in production throughout.

TL;DR

  • A codebase that is hard to read is a documentation problem, not a reason to rebuild.

  • The riskiest asset in a handover is the release pipeline (store accounts, signing material, CI), not the code.

  • Start with one senior engineer on a live sprint, overlap both teams, then scale.

  • Dutch apps handling personal data must account for GDPR and Vietnam's Personal Data Protection Law before access is granted, plus the Cyberbeveiligingswet (NIS2) if your company is in scope.

  • Judge success by an independent offshore release, not by hours logged.

About the Author: This guide comes from 724SOFTWARE, a Vietnam-based technology company with 200+ professionals (58% senior-level) and delivery experience across 10+ countries. Its mobile teams have shipped native iOS/Android, React Native and Flutter apps.

What does "moving an app offshore without a rebuild" actually mean?

It means moving development, release and maintenance of a live app to a new team while the codebase, architecture and store listings stay where they are. The code does not change hands in any meaningful sense. The knowledge of how to change it safely does.

That knowledge exists in three places:

  • The code and tests: visible, but rarely self-explanatory.

  • The pipeline: CI/CD configuration, signing certificates, App Store Connect and Google Play Console access, environment secrets.

  • People: why decisions were made, which modules break easily, which customers depend on odd behaviour.

A relay race shows why the third category is the hard one. Runners exchange the baton inside a marked zone where both are moving at speed. Batons get dropped when the incoming runner starts from a standstill. Tacit knowledge transfers the same way: only while both teams work the same live tickets. A cut-over date with a documentation handover is the standing start.

When is a rebuild actually justified?

Since most of what moves is knowledge, the next question is whether the code is worth keeping. Expert opinion: most rebuild requests are triggered by unreadable code, not broken code.

Signal

What it usually means

Path

 

"Nobody understands module X"

Missing documentation

Audit and document

Framework several major versions behind

Upgrade debt

Incremental upgrade

Crashes clustered in a few screens

Localised defects

Targeted refactor

Framework no longer supported against current store SDK requirements

Structural risk

Phased rewrite of the affected layer

Product strategy changed, most features unused

Product problem

Rebuild may be justified

Only the last two rows describe a real rebuild case. The rest are handover work.

What should be in place before the first offshore engineer starts?

A related but distinct question is preparation. Here the critical items are access and ownership, not code walkthroughs:

  • Store accounts owned by your company, not a former agency or freelancer.

  • Signing certificates and keys in a vault you control. Losing access to signing material can block releases.

  • Full repository history, transferred, not exported as a zip.

  • A build that can be reproduced on a clean machine, written down step by step.

  • A third-party inventory: analytics, payments, push notifications, backend APIs, with owners and contract terms.

  • A known-issues list from the outgoing team.

How should the handover be sequenced?

With access secured, the transfer itself runs in phases, each with an exit checkpoint:

Phase

What happens

Exit checkpoint

 

1. Audit

Offshore lead reproduces the build and maps risks

Risk register signed off

2. First seat

One senior engineer takes tickets from the live sprint

Pull requests merged after incumbent review

3. Shadow

Offshore team prepares a release, incumbent watches

Release approved in both stores

4. Reverse shadow

Offshore team leads, incumbent reviews

One release with no incumbent intervention

5. Scale

Add QA, a second developer or DevOps as the backlog requires

Velocity holds steady

At 724SOFTWARE the typical start is one senior engineer validated against a live sprint. Dedicated teams then scale from 1 to 50+ pre-vetted engineers within 2 to 4 weeks, and you interview the shortlist. Vietnam's 14:00 to 18:00 maps to the European morning, which is when shadow pairing happens. Outside that window, a Follow-the-Sun model with incident response under 10 minutes, 24/7, covers production issues.

What compliance rules apply when a Dutch app moves to a Vietnam team?

Stepping back from engineering, data protection is the gating question for many Dutch buyers. Netherlands companies must verify compliance with the EU General Data Protection Regulation (GDPR) for cross-border data transfers, the Dutch Cyberbeveiligingswet (NIS2) for supply chain security where they fall within its scope, and Vietnam's Personal Data Protection Law (Law No. 91/2025/QH15), in force since 1 January 2026.

In practice:

  • Decide which environments contain personal data. By default, give offshore engineers staging with anonymised or synthetic data.

  • Sign the data processing agreement and transfer mechanism before granting repository access.

  • If NIS2 applies to you, add the supplier to your supply chain risk assessment.

  • Ask for named standards. 724SOFTWARE is GDPR compliant and aligned with ISO 27001:2022 and ISO 9001 standards. Security and NDA setup is part of onboarding, and engineers work inside your existing repositories and tools, so you grant and revoke access through your own permissions.

Do AI coding tools make inheriting a codebase easier?

Building on the audit phase, yes: comprehension is where AI tools help most. 724SOFTWARE is a selected Anthropic partner in Vietnam and trains its engineers to use Claude Code in normal delivery work. Claude and Cursor support code review and refactoring. Gemini and NotebookLM support documentation and requirements synthesis.

Expert opinion: the most valuable use during a takeover is writing characterisation tests that pin down what the app does today, so a refactor later cannot silently change what users see. AI-generated explanations of old code still need checking against the incumbent team during the shadow phase. They are a draft, not a source of truth.

How do you know the handover has worked?

The central test is independence, measured by:

  • A store release shipped with no incumbent help.

  • Crash-free rate and store rating holding against your pre-transition baseline.

  • Escalations to the outgoing team falling to zero.

  • Visibility into delivery. At 724SOFTWARE, billing is based on actual working hours, and clients monitor team health and delivery performance directly.

Frequently Asked Questions

Can an offshore team take over a React Native or Flutter app?

Yes. 724SOFTWARE has shipped both, including Higher (React Native, 500,000+ downloads) and UTGL (Flutter mobile and web hub).

Will the team work in Dutch?

No. The whole team works in English, with Mandarin, Korean and Japanese also supported. Write tickets and documentation in English.

Does offshore mobile app development actually shorten delivery?

Treat that as an upper bound that depends on how well the handover is run.

Should we keep the previous agency during the transition?

Yes, at least through the reverse-shadow phase. Their review time costs less than a failed release.

Who owns the code after the move?

You should. Confirm IP assignment and store account ownership in the contract.

Is a long-term partner better than a project hire for this?

For a live app, yes. Maintenance never ends, and re-onboarding a new team every year repeats the whole transfer.

About 724SOFTWARE

724SOFTWARE is a Vietnam-based technology company that works as a long-term technology partner, delivering web and mobile development through dedicated teams, embedded staff augmentation and offshore development centres. Its 200+ professionals are 58% senior-level, and the company reports a 95% client retention rate. Mobile delivery includes MyVIB in-app trading and SHS Derivatives (iOS, Android, Web and Desktop from one team). All delivery is from Vietnam, GDPR compliant and aligned with ISO 27001:2022.

Next step

Before contacting any vendor, check one thing this week: does your company, not an agency, hold admin access to your App Store Connect and Google Play Console accounts and your signing material? If yes, you are ready to scope a first seat. Talk to 724SOFTWARE at https://724software.com.vn/.

Share this article

Product

Shrimpie Tran

AI Engineer

Keep Reading

Explore more from our experts.

View all

Stay ahead with our insights.

Get the latest on software design, strategy, and what's working in the field.

We respect your inbox. Unsubscribe anytime from any email.