Make access and knowledge visible
List the domain, hosting, source repository, editing system and connected services that apply to your site. Identify their owners without copying credentials into the inventory. Ask the incoming supplier what it can support and which parts need investigation. A willingness to log in is not the same as accepting responsibility for every undocumented integration.
Use a bounded transition rather than an instant promise
Start with inspection, a safe change and a recovery check. Agree any known exclusions and who remains responsible during the transition. Some legacy dependencies may require specialist support or replacement, but that conclusion should follow evidence. Keep routine maintenance, emergency support and future development as distinct responsibilities so a simple takeover does not become an undefined rebuild.
A practical check before you buy
In an appropriate preview or controlled environment, ask the incoming team to make one ordinary update and explain how it would restore the previous version. Confirm access ownership and the limits of support before extending the arrangement.
| Decision | What to consider | What to check |
|---|---|---|
| Access | Correct account owners | Verify permission without sharing secrets |
| Knowledge | Source and dependency records | Identify undocumented functions |
| Responsibility | Agreed support boundary | Document transition and exclusions |
An illustrative business scenario
A UK organisation changing marketing partners can separate website maintenance from ownership of advertising and analytics accounts.
This is an illustrative scenario, not a claim about an ImbaHub client or a promised result.
Discuss the right scope with ImbaHub
ImbaHub builds fast static websites with Astro, with editing through Imba CMS and Imba Builder. Start with the customer task described in this guide and ask which content, integrations and ongoing responsibilities your project needs. Agree the scope before comparing the investment.