← All articles

·3 min read

What to Ask About Source Code, Data Access and Handover Before Signing

Turn discussions about code, data and vendor access into deliverables a receiving team can verify.

Before signing with a software vendor, agree in writing who controls repository access, what code and data you receive, and how another team can take over. Ask the receiving team to demonstrate a build and restore a sample export.

Key takeaways

  • Review code usage terms and repository permissions separately.
  • Test what the data export includes and how it restores.
  • Name owners for account transfer and access removal.

What belongs on your contract review checklist?

TopicAsk in the meetingRecord for this engagement
RepositoryWho controls the organisation and access? Can we receive history and release tags?Account owner, access level, handover format and date
Code and licencesWhich components are created for us, vendor-owned or third-party?Component list, applicable terms and who confirms open questions
Business dataWhat can we export, in which formats, and with which attachments?Export scope, test procedure, delivery timing and retention arrangements
InfrastructureWho owns hosting, billing, domains and deployment accounts?Account owner, environment inventory and access transfer steps
OperationsCan another team build, deploy, monitor and restore the system?Runbooks, scripts, walkthrough and acceptance test
OffboardingHow will vendor access and shared credentials be handled?Owners, timing and evidence for access review and removal

Repository access and permission to use or modify components both need discussion. Give a qualified reviewer the actual agreement and dependency list when questions involve ownership or licensing. Canadian Intellectual Property Office guidance on software IP

How should you test a handover?

Ask the receiving team to build from the proposed repository delivery, deploy into a test environment and restore a sample export. In a fictional service portal, a useful export includes case IDs, messages and attachment references that can be matched after import. Verify that the team can answer a real support question using the handover materials.

For ongoing work, confirm how frequently the vendor will update the runbook and who will check that the latest release can still be built. Give each handover item an owner, due date and sign-off check.

What should happen when the engagement ends?

Ask who confirms the export, removes vendor accounts and transfers billing or infrastructure access. Prepare a short handover log with the date, responsible person and evidence for each change so teams can follow up on open items after the transition.

Use the software partner evaluation checklist to assess the wider delivery model. Review Wizy’s project governance approach.

Frequently asked questions

Is repository access enough to ensure software handover?

Repository access gives the next team a place to start. Check whether it also has the applicable usage rights, dependencies, build instructions and account access needed to maintain the system.

What should a complete software data export contain?

Agree on the records, identifiers, relationships, dates and attachments your team needs. Verify completeness by restoring a sample and matching the results to the source.

Who should own the production accounts after handover?

Identify the organisations responsible for hosting, billing, domains and deployment in the agreement. Test that the receiving team can perform agreed operational tasks with its own accounts.