There is a question clients sometimes hesitate to ask, usually somewhere near the start of a relationship: if we ever wanted to leave, how hard would that be? It is a fair question, and we would rather answer it in writing than let it hang in the air.
The answer is: not hard at all. Any client of ours can ask, at any time, for a complete export of their site. Code, database, files, everything the site is, packaged together with a restore script that brings the whole thing up with a single command, on infrastructure that has nothing to do with us. We recently made this a standard, rehearsed part of how we offboard, but it is not an end-of-relationship feature. It is a standing right, and this article explains how it works and why we built it.
What is actually in the package
A handover package contains the three things a website is made of. The code: everything that was built for you, along with the exact versions of everything it depends on, so the result is reproducible rather than approximate. The database: your content, your users, your settings, the accumulated state of the site. The files: every image, document, and upload your team has added over the years. Alongside them sits a restore script and a short set of instructions.
The script is the part we are quietly proud of. Handover exports have a reputation in our industry for being an archive that lands in a folder and is never opened again, a box of parts with no assembly manual. Ours reconstructs a running copy of the site with one command on a standard server. Whoever receives it, whether that is a new provider, an internal team, or a consultant reviewing our work, does not need to know how our platform is put together. They need one command and the patience for it to finish.
We also include the operational notes a successor would want on day one: how the site is built and deployed, which scheduled tasks it runs, and the third-party services it talks to. Not a novel, just the page we would want to receive if the roles were reversed.
Rehearsed, not theoretical
A promise like this is only worth something if it is tested, so we treat handover the way we treat backups: a restore that has never been rehearsed is a hope, not a plan. When we prepare an export, restoring from it is part of preparing it. The package that reaches you is one that has already been brought back to life, not one we believe should work.
That habit came out of making offboarding a defined process rather than an improvisation. Goodbyes are rare, but we wanted the last experience a departing client has with us to be as tidy as the first one. The same discipline turns out to pay off in far less final situations too, which brings us to the more interesting point.
Available any time, not just at the end
Nothing about a handover package requires anyone to be leaving. Clients ask for exports for their own continuity planning, because an auditor or an insurer wants evidence that the organization does not depend on a single supplier, because an internal policy requires a copy of critical systems held in their own hands, or simply because it feels prudent. All of these are good reasons, and none of them need justifying to us.
If you want an export every quarter for your own records, that is a service we are glad to provide, not a warning sign we quietly monitor. Your site is yours. The clue is on the invoice: you paid for it.
It is worth separating this from backups, because the two answer different questions. Backups protect you from accidents, run automatically on our platform, and get their restores rehearsed. A handover package answers the independence question: could this site live somewhere else, run by someone else, starting from nothing but a box of files? Both matter, and having one does not substitute for the other.
Why we volunteer to make leaving easy
The honest answer is that lock-in is bad for the client and, over time, bad for the agency too. A relationship held together by exit costs stops being tested by the quality of the work, and everyone involved can feel it. We would rather be kept by our own performance. If the work is good, the availability of the exit changes nothing. If the work ever stopped being good, you would deserve the exit.
There is also a quieter effect we have come to appreciate: knowing that any client could take a complete, working copy of their site elsewhere keeps our own house in order. Code gets written as if someone else will read it, because someone else might. Documentation stays current, because it ships. Portability turns out to be a quality bar disguised as a courtesy, and we are happy to be held to it.
What this feels like from your side
In practice, the ownership question stops taking up mental space. You can enter a long-term arrangement without the small-print anxiety, because the exit is defined, tested, and costs nothing more than asking. Budget conversations get easier when the alternative is real rather than hypothetical, for both sides. And handovers inside your own organization get easier too: when a new manager inherits responsibility for the website, being able to say that a complete restorable copy exists, from a supplier who rehearses producing it, settles the room.
It also changes the tone of the years in between. A partnership where either side could walk away cleanly, and neither wants to, is a healthier thing to build on than one held in place by friction. The work has to keep earning its place, which is exactly the pressure good work thrives under.
The confident version of loyalty
We want clients who stay because staying is the best option on the table, year after year. That is a higher bar than staying because leaving is hard, and we prefer it that way. It keeps us honest about quality, responsive about service, and humble about the fact that trust is renewed, not owned.
None of this is a radical idea. Portability is how the wider software world already treats serious infrastructure, and websites deserve the same standard. The only unusual part is writing it into the service description and rehearsing it, so the promise is still true in the tense week when someone finally needs it.
If you are weighing up a long-term partner for your site and wondering what happens at the edges of the relationship, ask about the handover package in the first conversation, with us or with anyone. It is a revealing question, and we like being asked.