How do I move my app studio’s client repositories to a buyer without breaking anything?

Start with a list. For every client repository, record its name, the client it serves, who owns the code under the contract, where it is hosted and who has access. Some repositories belong to the client and merely sit in your account. Others are your own shared libraries that several projects use. Do not move a client’s code without confirming whose it is.

Next, map the hidden dependencies. Automated builds, deployment keys, webhooks, issue trackers and scheduled jobs often point at the old location. List them for each project. Secrets such as keys and tokens should be replaced in the new place, not copied out of old files, and the old ones should be retired once the new setup works.

Then move in a sensible order. Begin with a quiet project, learn from it, and only then move active ones, ideally between client releases. After each move, run a full build, a test deployment and a check that the history is intact. Tell clients ahead of time if their access is changing. Keep the old home read-only until every project has been confirmed. Keep a written log of each move, with the date, the person responsible and any surprises, so the next one goes faster.

Key takeaways

• Confirm whose code each repository holds before moving anything.
• List builds, keys and webhooks that point at the old location.
• Move a quiet project first, then active ones between releases.
• Keep the old location read-only until every project is verified.