What You Actually Receive in a Source-Code Software Handover
Short answer
A source-code software handover delivers the application repositories for the agreed scope, the database schema with versioned migrations, deployment files such as Docker Compose and Nginx configuration, documented environment variables, transfer of the credentials the buyer owns, setup documentation and the support terms. What it does not transfer is copyright or resale rights unless the licence says so, or responsibility for hosting and third-party accounts.
'You get the source code' is the start of the conversation
Two buyers can be told the same sentence and receive very different things: one gets a zip file, the other gets a running deployment on their own server with the repositories, the database, the deployment scripts and a written account of how it fits together. The software handover checklist exists because the second outcome has to be specified. This article walks through each item and why it is there.
The deliverables, item by item
- **Application repositories** for the agreed scope — frontend, backend or API, admin dashboard and, where included, mobile application source — in a version-controlled form the buyer's team can clone.
- **Database schema and migrations** — the schema as versioned migration files, not a one-off dump, so the buyer's team can evolve it. Dino HRMS, for example, ships MySQL migrations that are versioned and checksummed.
- **Deployment files** — Docker Compose definitions, Nginx reverse-proxy configuration and the scripts used to bring the stack up on the buyer's server.
- **Environment configuration** — every environment variable documented, with the buyer's own values entered for gateways, mail, storage and keys.
- **Credentials transfer** — server, domain, database and third-party accounts in the buyer's name, with TechDino's access removed at handover.
- **Documentation** — setup, deployment and operational notes for the delivered scope.
- **Support terms** — three months of technical support from the confirmed delivery date, with the exclusions stated in writing.
What a handover does not transfer
Source-code access is not copyright transfer, and it does not by itself grant resale or redistribution rights. The permitted use, modification and resale terms are in the licence for that product, which is why the source code and licensing guide separates the three. Hosting, domain registration, SMS, email, maps and payment gateways are billed by those providers and remain the buyer's accounts.
Migration assistance: what 'basic' means
Basic setup, deployment and database migration assistance is included for moving the application to a supported hosting environment. It covers getting the delivered stack running on the buyer's server and importing the buyer's initial data in the delivered schema. It does not cover re-engineering data from an unrelated legacy system; that is quoted as scoped work.
How to verify a handover in one sitting
| Check | How |
|---|---|
| The repository builds | Clone it on a machine TechDino has never touched and run the documented build. |
| The database is reproducible | Run the migrations against an empty database and confirm the application starts. |
| The deployment is yours | Log in to the server, the domain registrar and each third-party account with credentials only you hold. |
| The branding is applied | Open every interface — customer, admin, staff — and confirm no TechDino name or asset remains. |
| The support terms are written | The delivery date, the three-month window and the exclusions are in the signed scope. |
Why this list is in every TechDino scope
A ready-made product is only cheaper than a custom build if the buyer can run it without the vendor. Each item above removes one way the buyer could be dependent: no migrations means no schema changes; no deployment files means no second server; no credential transfer means no real control. Setup is estimated at approximately two weeks after scope, assets and access are confirmed. Pricing is quoted on scope rather than published; send the requirement through the contact page and TechDino returns a written quotation after a walkthrough.
Frequently Asked Questions
Do I receive the complete source code?
Yes — the complete source code included in the agreed project scope: available frontend, backend, admin dashboard, database schema and any included mobile application source.
Can my own developers modify the delivered code?
Yes, within the licence for that product. Modification for your own use is the normal case; resale or redistribution requires express written permission.
Is the handover the same for every product?
The checklist is the same; the interfaces differ. A product whose scope includes a mobile app hands over that source too; a web-only product does not.
What happens after the three months of support?
Support beyond the included period, and future maintenance, are agreed separately in writing; the [support and maintenance guide](/resources/support-and-maintenance) sets out the options.
Need Setup or Custom Coding?
Get in touch to rebrand or customize our ready-made products, or discuss custom development services. All quotes are customized and private.
Related Articles
How Source-Code Licensing Works for Ready-Made Software
What buying software 'with source code' actually means: license types, what you can and cannot do, deployment rights, and questions to ask before paying.
White-Label Software for UAE and Gulf Businesses: Payments, Hosting and Delivery
What changes when a UAE, Saudi or Gulf business buys ready-made white-label software: AED and SAR billing, regional payment gateways, hosting residency questions, timezone coordination from Hyderabad, and what is confirmed in the written scope.