Empower growth and innovation with the latest Website Dev insights

The final payment is not settled and the client is pressing for source code and backend account, while the contract only says 'one website'—should we hand them over?

Nov 22, 2026 Read: 8

Let’s start with the conclusion: whether to hand over the source code and backend account for a custom official website does not depend on how urgently the client is pushing, but on how far the 'deliverables' are written in the contract. Based on common project delivery practice in 2026, it is relatively common practice to hand over a 'runnable deployment package + database export + account list + license notes' after the final payment is settled and the acceptance form is signed; only when the contract explicitly states 'source code transfer' or 'copyright belongs to Party A' does the ownership of the entire codebase come into play. Commercial templates, paid plugins, licensed fonts and third-party API keys are usually not transferred as part of the whole site package; they need to be listed separately with the scope of license.

Remember one boundary: the handover of accounts and data is the bottom line; code ownership is a negotiable clause. Discuss the two separately, and there will be much less arguing at the final payment stage.

'Giving source code' actually includes four things—break it down before negotiating

When clients say 'give me the source code,' what they actually need is often only one or two of these. If only the backend super admin account is provided, the client cannot get the database structure when changing vendors, and migration requires redoing columns and content, commonly costing 10% to 30% of the original development cycle (experience range); conversely, if only code is delivered without accounts, and the domain and server are still under the original vendor’s name, the client still cannot move.

  • Frontend templates and styles: page structure, stylesheets, image and video assets
  • Backend program and database: business logic, data table structure, published content
  • Environment and deployment: server configuration, runtime version, pseudo-static and redirect rules, scheduled tasks
  • Accounts and keys: domain registrar, server and cloud platform, ICP filing entity, CMS super admin, analytics, maps and SMS, payment and other third-party keys

The benefit of listing them separately is that you do not have to get stuck on a big term like 'whether to give source code'; you can confirm item by item which must be handed over and which only involve usage rights. The criterion should be 'whether someone else can take over and get the site running,' not how large the zip file is.

Why does this always turn into an argument at the final payment stage?

The deliverables column in contracts often says 'one corporate official website (including design, development, and launch)' without breaking it down to file level; sales says orally 'it’s all yours,' and Party A understands it as a buyout; at final payment, Party A wants the package, while the delivery side worries that the code will be reused in competitor projects, and both sides think they are right. The core of the dispute is usually not attitude, but the delivery granularity was not made clear when the contract was signed.

I once encountered this at a delivery site: in 2026, for a custom project with a 6-8 week cycle and a budget in the tens of thousands of RMB range, the client’s IT department suddenly required to take over by itself after launch, while the contract only said 'one website.' The constraints were that the final payment was unsettled, the code still contained third-party components with annual fees, and the client had no dedicated operations staff. The approach was to first produce a handover list, listing the deployment package, database export, accounts and license notes item by item, marking clearly what could and could not be transferred, and then schedule a half-hour online handover. As a result, the client accepted a two-step approach: accounts and data first, and code within 5 business days (experience range) after the final payment was settled. The cost was spending an extra 2-3 business days organizing documents and running a migration drill, and the final payment was delayed by about two weeks.

So a more practical judgment is: whether the delivery list was included as an attachment before the contract was signed. If this is done, there will basically be no rehashing of old issues at the final payment stage; if not, the only option is to supplement documents afterward in exchange for a signature.

Break 'giving source code' into four checkable lists

Based on delivery experience, breaking it into four lists is more workable than saying 'I’ll give you the source code.' The division is based on 'who will use it in what scenario': technical operations needs the runtime list, marketing operations needs the account list, legal needs the license list, and business needs the boundary list. Each item should have a file that can be opened or an account that can be logged in; verbal explanations often do not count.

  1. Runtime list: deployment package or code repository address, database export file, environment and version notes, pseudo-static and redirect rules, scheduled task configuration
  2. Account list: domain registrar and expiration date, server/cloud platform, ICP filing entity and access information, CMS super admin, analytics and webmaster platforms, third-party API accounts
  3. License list: commercial font license, stock image authorization, paid template or plugin license, open-source components and license types
  4. Boundary list: what is not transferred with the site (original manufacturer authorization, annual paid services), what is billed separately (secondary development, migration assistance), what depends on the original vendor (proprietary modules, encrypted components)

Among the four lists, the license list is often skipped, and problems often appear half a year later: licenses for fonts, stock images and templates are often tied to the using entity or number of sites; if the client uses them for a new site or for a subsidiary, it may exceed the licensed scope. Archiving license certificates together at delivery saves trouble compared with explaining later.

Whole-site transfer vs. only usage rights: where do cost and risk differ?

Both approaches are common; the key is whether the client has the ability to take over. Before negotiating, ask 'who will maintain it after taking over,' and the answer often determines which option to choose.

  • Whole-site source code transfer: suitable for enterprises with internal IT or a long-term outsourcing team; the delivery cycle is commonly 5-10 business days after launch (experience range), and the quote may include 10% to 30% (typical range) of organization and documentation costs; the benefit is freedom to migrate, and the risk is code leakage and reuse
  • Only backend usage rights: fast delivery, commonly 1-3 business days (experience range), and the fee is usually already included in the development payment; suitable for enterprises that treat the official website as a showcase and will not do secondary development in the short term; when changing vendors, they need to redevelop or buy out on a per-case basis, and migration costs are hard to estimate in advance
  • Compromise approach: hand over the deployment package and database, but not build scripts and internal tools; transfer all accounts and regenerate keys
  • Common premise: the domain, ICP filing, and server accounts should usually belong to Party A’s entity; this item is generally not recommended as a bargaining chip

When comparing, do not look only at the quote; look at the actual cost of one migration: for sites with content within a few hundred articles, re-importing is often counted by day; for sites with membership, orders, and multilingual data, migration is often counted by week. This is also the reference line for judging 'whether this source code is worth fighting for.'

When should handover be discussed, and when is it unnecessary to force it?

The scenarios suitable for discussing source code handover are relatively clear: the client has internal IT or a stable technical partner, the business requires secondary development, internal audit or security checks are needed, a vendor change is planned, or the group requires unified asset registration. In these cases, writing the list into the contract saves cost compared with arguing afterward.

  • The site uses SaaS website building or a template-licensed site, and the platform itself does not provide source code
  • The client has no maintenance capability; even with the code, no one will take over, which instead increases security risks
  • The contract has clearly stated annual payment and only purchase of usage rights
  • The pages contain third-party paid components, and transfer itself may violate the original manufacturer’s license

A boundary to remember: ownership of accounts and data takes priority over ownership of code; whether to give code can be negotiated, but the domain, ICP filing, database and inquiry data must have a clear handover. For personal information such as inquiry phone numbers, it is advisable to desensitize during export or attach a data processing note; do not send the entire database zip file directly through chat tools.

FAQ

If the contract only says 'one website,' is it reasonable for the client to still ask for source code after the final payment is settled?

It is not outrageous, but there is a lack of clause basis. A common approach is to negotiate a supplement by attachment: hand over the deployment package, database, and all accounts; build scripts and internal tools can be discussed separately; both parties sign a supplementary handover list.

Is delivery complete if only the backend super administrator account is provided?

Not complete. An account is only an entry point; if the database structure, environment configuration and third-party keys are not handed over, the client will still have to redo things when changing vendors. The acceptance criterion should be written as 'migratable' rather than 'can log in.'

The database contains client inquiry phone numbers—can the whole database be sent over?

It can be handed over, but minimize according to purpose: export with desensitization or attach a data processing note, clear test data and irrelevant logs, and do not send the entire database zip file directly through chat tools.

If paid templates and commercial fonts are used, can the source code be packaged together?

Usually it cannot be transferred as a whole package. Licenses for templates and fonts are often tied to the using entity or number of sites; attach license certificates and scope at delivery, and let the client purchase the parts beyond the license itself.

If the client breaks the site after delivery, is the original developer still responsible?

It depends on the maintenance clause in the contract. A common practice is to enter a 1-3 month (experience range) issue-fixing period after handover; data recovery caused by human error is billed per case, as long as it is written clearly in advance.


If you are about to sign a contract or make the final payment, first break the deliverables into four lists—runtime, accounts, licenses, and boundaries—and attach them to the contract, ticking each item before signing acceptance. For projects with a tight budget and a client without maintenance capability, writing 'only usage rights + all accounts handed over' clearly is usually more practical than fighting over source code. When implementing projects, Xiyue Company generally uses this list for handover records and keeps a copy for the client’s archive.

Interested in this topic?
10-year tech team — reference proposal within 24 hours
Obtain Proposal
Are you ready?
Then reach out to us!
+86-13370032918
Discover more services, feel free to contact us anytime.
Please fill in your requirements
What services would you like us to provide for you?
Your Budget
ct.
Our WeChat
Professional technical solutions
Phone
+86-13370032918 (Manager Jin)
The phone is busy or unavailable; feel free to add me on WeChat.
E-mail
349077570@qq.com
Submitted successfully
Thank you for your trust. We will contact you soon!
Recommended projects for you