When the engineer who runs your SaaS app gives notice, sharing the code repository is only part of the handover. Their replacement also needs access to the hosting account, the domain, and the database so they can release a fix or recover customer data during an outage.
Start by regaining access and proving that the team can operate the app. A long document is less useful than a new engineer successfully deploying a change, finding an error, and restoring test data.
You can spread these checks across the first month. Allow more time for systems that still depend on the departing engineer.
First, make sure the company can reach its own systems
In this example, the departing engineer has been the only person to release the API, manage the domain and database, and maintain the payment setup. Before they leave, have a second person check that the company can reach each account and do the work it needs there.
Begin with company-controlled access to the source repository, hosting account, database, domain registrar, DNS, identity provider, payments, and email delivery. Confirm that account recovery messages go to an address the company will keep.
Have the new owner sign in and open the settings they need for their work. In the handover notes, record the account, who owns it, and how to regain access. Store the actual keys in the team's approved secret store.
Review service accounts and API keys too. Before rotating an unfamiliar key, find what uses it. A sudden change can break a deploy script or payment callback that nobody has identified yet. Replace access in a controlled order, test the replacement, and remove the old access when it is no longer needed.
If you need to remove access right away, tell the people who run the affected systems. Find out what the key controls and agree on how to get the app working again if a job or release breaks.
In the first week, release one harmless change
Ask the new owner to follow a commit from the repository to the running app. They should be able to find the production branch, build settings, runtime settings, and place where the release result appears.
For a Forte Service, have the new owner open a release in its deployment history and follow the commit through the recorded stages and output. That gives them a way to trace the running code when they take over.

Then deploy a harmless change through the normal review process. The exercise should answer who approves it, how the team knows the new app is healthy, and which version now receives traffic.
Also check how to return to the previous version. Forte can return eligible failed updates to a prior healthy revision, but an old container cannot undo a destructive database change. The new owner needs to understand the app's schema rules as well as the deployment controls.
If the release depends on an unwritten command on someone's laptop, record and fix that gap. The goal is for the second person to repeat the process with company-owned access.
In the second week, test a restore
Ask which data would be hardest to lose. For our example SaaS, that might be customer project records, uploaded files, and the state used to decide paid access.
For each store, establish how often data is backed up, how long backups remain, and who can request a restore. Then test the process in a safe environment. Confirm that the app can read the recovered records and that a person knows how to connect the app to them.
A backup's existence does not tell you how long customers will wait. Record the steps that took time and any data that could be missing. If recovery needs provider support, include that handoff in the plan.
On Forte, the database tier changes how restores work. Shared databases have daily backups retained for seven days and support-assisted restores. Dedicated PostgreSQL is in closed alpha and requires approved access. It adds point-in-time recovery within its configured retention window. A dedicated restore creates a new database, and existing Service connections stay on the source until you change them. Managed databases are Open Beta. Check the current database guide for the tier you use.
Repeat the same practical approach for a failed request. Create a safe test failure, find its request record, and follow the relevant logs. The engineer should leave knowing where to start an investigation, rather than only knowing that monitoring exists.
In the third week, give alerts an owner
If an alert still goes to the engineer who left, the rest of the team may never see it. Check where it goes, who reads it, and what they should do when it fires.
For our example app, a database error alert should lead to the API that has the problem and its connection settings. A failed payment event should lead to the handler and a way to check whether access was updated. An email that says only “something is wrong” leaves too much work for the recipient.
Review the customer paths that matter most: sign-in, saved changes, billing, and any scheduled work. Ask how the team would learn that each one stopped working. Support reports may be part of the answer, but they should not be the only way to detect a serious failure.
Then remove alerts that have no useful response or update them so they point to a decision. Record an escalation route for problems the first person cannot resolve. Make sure the route survives holidays and staff changes.
In the fourth week, connect costs and renewal decisions
Review the invoices and commitments with the people who can approve spending. Find normal charges, upcoming renewals, and any resource whose purpose is unclear.
A domain renewal may cost little compared with your cloud bill, but missing it can take the product offline. Give it an owner who knows when it renews and which account pays for it.
If the old setup depends on many custom scripts and tools, check which ones your team could retire by moving the app to one platform. On Forte, the Service's repository, release history, settings, and request diagnostics follow a common workflow. That can reduce the amount of private knowledge a new engineer must learn.
A migration belongs after access and restores are understood. Moving an app you cannot currently restore adds risk. Follow the staged migration guide if a move becomes part of the plan.
Finish with a short record someone has used
Keep a short record of where each app runs and where its data lives. Explain how to release it, find a failure, and recover. Include the owner and the gaps still open. Link to the provider's current guide rather than copying pages that will become stale.
Have the new owner use the record during the exercises and note when they still need help from the departing engineer. Add the missing steps or account details while both people are available.
Schedule another release and restore test after the handover. A working process can drift when dependencies, keys, and people change. Repeating it helps the team notice before an outage forces the test.
If credit expiration is part of the handover, use the AWS credit review alongside the cost work. For help moving a suitable app after the review, see Forte migration support.