Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My company bought another one and the two systems must work together

Short answer

Do not merge anything first. Make a written inventory of both systems: who owns each account, where the data lives and what depends on what. Then choose a path: keep both and connect them, move one into the other, or retire one. Apps can change developer accounts through Apple and Google transfers, but servers and data move separately.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I now have two customer lists, two logins and two sets of reports.
  • Staff re-type data from one system into the other.
  • Nobody knows who owns the app or server accounts of the company I bought.
  • The acquired company's developer left, or is the only person who knows how it works.
  • I am being asked to switch one system off by a certain date.

Why does this happen?

  1. Each system grew on its own plan

    Two companies choose different databases, hosting, login methods and naming. The same customer can exist twice with different details, so a simple copy of data creates duplicates and mistakes.

  2. The accounts may belong to people, not the company

    An app can be published from the developer's own store account. Apple lets an app move to another account while it stays available, and its reviews, ratings and updates continue, but only the Account Holder of the current account can start it.

  3. Google Play moves the listing, not the whole system

    Google transfers the app's users, download statistics, ratings and reviews, content ratings and store listing to the new account. Earnings and payout reports do not move, so they must be downloaded first.

  4. A transfer does not move the servers or the code

    A store transfer moves the listing. Source code, servers, databases, push notification keys, analytics and the domain are handed over separately, and an app can look transferred while it still depends on the old company's accounts.

What can I do about it today?

  1. Freeze changes on both systemsAsk both teams to stop deploying non-urgent changes until the inventory is done. It keeps the picture stable.
  2. List every account and who holds itApp store accounts, hosting, domains, databases, payment provider, email service and source code. Mark any held by a person who may leave.
  3. Get written handover from the acquired company's technical personAsk for documents, logins held by the company and a short call. Do this while that person is still available.
  4. Ask for backups, and ask who has tested a restoreA backup nobody has restored is only a hope. Ask your current developer to say when it was last tested.
  5. Write down what the merged business needsOne customer list? One login? One invoice? Rank them. This decides the technical plan.
  6. Do not agree a switch-off date yetWait for the plan. A date set before the inventory usually has to be moved.

When should I bring someone in?

  • Customers or payments exist in both systems at the same time.
  • The only person who understands one system is leaving.
  • A deadline, such as a contract end or hosting expiry, forces a decision.

How do I handle it?

  1. Read both systemsI review both codebases, databases and hosting set-ups and write a plain-language map of each.
  2. Present three optionsIn writing: connect them, move one into the other, or retire one. Each option lists the work, the risks and what stays untouched.
  3. Map the dataCustomers, orders and users are matched field by field, with a rule for duplicates that you approve.
  4. Move in small steps with a backup firstA trial move on a copy comes first, then the real one, with a tested way to roll back.
  5. Retire the old system lastIt is switched off only after the new one has run the real work, and after the accounts are in your company's name.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Should I keep one system and drop the other?

It depends on the code, the data and the business needs. I compare both and give the options in writing instead of picking in advance.

Can the acquired app move to my store account?

Yes, both stores support transfers if their criteria are met, and the current account owner has to start it. The server and data are a separate task.

How long will the merge take?

It depends on the size of both systems, and I only give a time after reading them.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.