Monday, 7.30 a.m., your first day as the owner. The bookkeeper cannot log in to the ERP system because her password has expired. Only the administrator can reset it, and until Friday that was the seller. He is on a plane. The password is on a slip of paper in his office, perhaps.
Many takeovers of small companies start like this. This article shows you which logins and documents you need to hold on day one, what follows in the first 30 days and what can wait until day 100. It picks up where our business acquisition checklist ends: after closing.
Why IT becomes a risk after buying a business
A company with 5 to 50 employees rarely has an IT department. It has the owner, who ordered the server twelve years ago, and an acquaintance who “looks after the computers”. Both know a great deal. Very little of it is written down.
We come across three things again and again in takeovers:
- Knowledge in the seller’s head. He registered the domain, set up online banking and signed the contract with the software supplier. Often all of this runs through his private e-mail address or his mobile number.
- Systems that have grown over time. An industry application from 2011, Excel lists beside it, a network drive and three cloud services that someone once subscribed to with the company credit card.
- An IT service provider without a contract. He comes when called and invoices by the hour. What he looks after, how quickly he has to respond and who owns the passwords is not recorded anywhere.
As long as the seller is in the building, this works. With the change of ownership, the person who held everything together is gone. For buyers who come from outside, as in a management buy-in, the risk is greatest: they know neither the systems nor the people behind them.
Before signing: what the purchase agreement should say about IT
The IT review itself belongs in due diligence. How to set it up is covered in our article on due diligence in a business acquisition. This section deals with three points you should settle before signing, because afterwards you have very little leverage.
Access and documentation as a closing condition
Agree that at closing the seller hands over a list of all systems together with the administrator logins. This covers the domain, e-mail, ERP, online banking, website, telephony and the social media accounts. The list is checked on closing day: someone logs in once with every account.
Support from the seller after the handover
Record in writing for how long and to what extent the seller remains available for questions, and whether this is included in the purchase price. Without such a clause you depend on his goodwill. It is usually there, but it fades once the purchase price has been paid.
Share deal or asset deal: what happens to licences and contracts
If you buy the shares (share deal), the company remains the contracting party. Software licences, hosting and maintenance contracts generally continue. What you need to check are clauses that give the provider a right to terminate on a change of control.
In an asset deal you take over individual assets and contracts. Employment relationships pass to the buyer with the business by law, unless the employees decline the transfer (Art. 333 CO). This does not apply to other contracts: you can only assume obligations with the consent of the other party (Art. 176 CO). Whether a software licence can be transferred is set out in the vendor’s licence terms. This depends on the individual case and should be reviewed by a lawyer before signing.
Day 1 to 7: taking control of access and backup
In the first week you change nothing in the way the company operates. You make sure that it also belongs to you technically.
Moving administrator access to the company
Go through the list from closing and switch every login to an address and a phone number that belong to the company. The order follows from one question: what would leave you unable to act most quickly?
- Domain and DNS. Whoever holds the domain controls e-mail and the website. The company should be registered as the holder, even if the seller once registered it privately.
- E-mail and user management. With Microsoft 365 or Google Workspace you need an administrator account of your own. The previous one stays in place for now, with a new password.
- ERP and accounting. This includes the account with the software supplier, so that you receive support.
- Online banking. Signing authority changes with the entry in the commercial register. The bank needs its own forms and some lead time. Clarify before closing who pays salaries and suppliers in the meantime.
- Website, social media, telephony. Less urgent, but often tied to private accounts and therefore tedious once the seller can no longer be reached.
Cleaning up old accounts and switching on multi-factor authentication
Almost every company has active accounts of people who left years ago. Disable them. You disable the seller’s account on the day his involvement ends. If there is a transition period, he receives an account with standard rights for that time.
Then switch on multi-factor authentication for e-mail, remote access and all administrator accounts. The Swiss National Cyber Security Centre (NCSC, now the Federal Office for Cybersecurity) lists it among its five immediate measures for companies, together with daily backups, updates, caution with e-mails and secure passwords.
Restoring from the backup for real, once
“We have a backup” is the sentence I trust least after a takeover. In the first week, have one file, one mailbox and the ERP database restored as a test. Only then do you know whether the backup runs, what it covers and how long a restore takes.
The NCSC recommends keeping at least one copy offline and at an external location and practising the restore from time to time (baseline protection for companies, in German). If there is no offline copy, that is your first investment.
Day 8 to 30: recording systems, contracts and key people
Now you build the overview that so far existed only in the seller’s head. A spreadsheet is enough.
An inventory of all systems, licences and subscriptions
For each entry, record what the system is used for, who looks after it, what it costs, how long the contract runs and by when notice must be given. The quickest sources are accounts payable and the credit card statements of the past twelve months. The subscriptions nobody remembers show up there as well.
Conclude a written contract with the IT service provider: scope of services, response times, hourly rate and the duty to hand over all passwords and configurations to the company.
Who can do what? Making single-person knowledge visible
In every area, ask who steps in if the person responsible is away for three weeks. Where nobody is named, you have found knowledge held by one person only. It often concerns payroll, the interface between the ERP and the online shop, or the control system of a machine.
Have that person write down their procedures in bullet points and have someone else carry them out once. It takes little time and is the cheapest insurance you will take out this year.
Data protection: record, processors and customer data
In a share deal the company remains responsible for its data processing, with you as the new owner. You should know three points within the first month:
- Record of processing activities. The Federal Act on Data Protection requires such a record (Art. 12 FADP). Companies with fewer than 250 employees are exempt, unless they process sensitive personal data on a large scale or carry out high-risk profiling (Art. 24 DPO). A simple list is still worthwhile: it shows you where customer and employee data are kept.
- Processors. Cloud providers, the payroll office and the IT service provider process personal data on your behalf. This needs a contractual basis, and you must satisfy yourself that they are able to guarantee data security (Art. 9 FADP).
- Data security and notification duty. The company must protect its data with appropriate technical and organisational measures (Art. 8 FADP). A breach that is likely to lead to a high risk for the people affected must be reported to the Federal Data Protection and Information Commissioner (FDPIC) as quickly as possible (Art. 24 FADP).
In an asset deal, customer data move to a new controller. Whether and how customers have to be informed depends on the individual case and should be clarified with a specialist.
Day 31 to 100: stabilise first, then modernise
After a month you know the weak points and you have ideas. Keep to the order: security first, then stable operations, modernisation last.
The order of work
Security covers the points from the first week plus updates for operating systems, the firewall and the industry software. Operations cover the contract with the service provider, deputies and the replacement of devices whose failure would stop work. Everything else goes on a list for later.
Typical wrong decisions in the first months
The most common one is replacing the ERP system in the first six months. The old system is cumbersome, so it has to go. But you do not yet know the processes well enough to set up a new one properly, and the employees are already coping with a change of owner. Our checklist advises against major changes in the first 100 days unless they are unavoidable. This applies to IT in particular.
The second is replacing everything at once: telephony, e-mail and server in the same quarter. If something fails, nobody knows which change caused it.
If you change the accounting software later, think of the old data. Accounting records and vouchers must be retained for ten years and remain readable for that long (Art. 958f CO).
Budget and priorities for the first year
On day 100 there is one page on the table: the five to ten most important measures, each with cost, benefit and deadline. Obtain quotes before you put in figures. If a larger replacement is due, it belongs in your liquidity planning and possibly in the conversation with the bank. How investments after the purchase fit into the financing is covered in our article on financing a business acquisition.
The 100-day plan for IT at a glance
| Period | Task | Responsible | Result |
|---|---|---|---|
| Before closing | Agree the handover of access and the seller’s support in the contract | Buyer, legal adviser | Clauses in the purchase agreement |
| Day 1 | Check and take over administrator access | Buyer, seller | Every login tested once |
| Day 1–7 | Move access to the company, disable old accounts, switch on multi-factor authentication | Buyer, IT service provider | No login depends on a private individual |
| Day 1–7 | Test a restore from the backup | IT service provider | Log with scope and duration |
| Day 8–30 | Draw up the inventory of systems, licences, subscriptions and contracts | Buyer, accounting | List with costs and notice periods |
| Day 8–30 | Record single-person knowledge and appoint deputies | Buyer, team leaders | Procedures documented in bullet points |
| Day 8–30 | Review data protection: record, processors | Buyer, specialist if needed | Overview of personal data and contracts |
| Day 31–100 | Catch up on updates, conclude the contract with the IT service provider | Buyer, IT service provider | Stable operations with clear responsibilities |
| Day 100 | Set priorities and budget for the first year | Buyer | One-page list of measures |
Common mistakes when taking over IT in an SME
Relying on verbal assurances. “Just call me if anything comes up” does not replace a handover list. What is missing on closing day takes effort to obtain later.
Leaving the seller with administrator rights. Out of politeness his account stays active for months. In a dispute, an outsider then has full access to e-mails and customer data.
Never testing the backup. That the backup has been running into nothing for months only becomes apparent on the day you need it.
Replacing the IT service provider in the first month. He is often the only one who knows the set-up. First conclude a contract, have everything documented, and decide afterwards.
Modernising too early. New software does not solve a problem you have not yet understood. Those who listen first invest with better aim later.
Frequently asked questions about IT after buying a business
What do I need to check in IT on the first day after buying a business?
Check that you can log in to the domain, e-mail, ERP and online banking with an administrator account of your own. Switch the recovery addresses to the company and change the previous administrator’s password. Have someone show you where the backup is kept. Everything else can wait until the second week.
Do software licences transfer automatically when a business is bought?
In a share deal the company remains the licensee and the licences usually continue, subject to change-of-control clauses. In an asset deal contracts do not transfer by themselves: the provider has to agree, and the licence terms determine whether a transfer is permitted. Have this checked before signing.
How long should the seller remain available after the handover?
There is no statutory rule; what counts is what the purchase agreement says. I recommend agreeing availability in writing for at least the first 100 days, including scope, response time and remuneration. The more knowledge only the seller holds, the longer this phase should last.
Does a small SME have to keep a record of processing activities?
Under Art. 24 of the Data Protection Ordinance, companies with fewer than 250 employees are exempt as long as they do not process sensitive personal data on a large scale and do not carry out high-risk profiling. The other duties under the Federal Act on Data Protection still apply, for example on data security and processors.
Conclusion: keys first, renovation later
IT rarely decides whether a business acquisition succeeds. It does decide how calm the first months are. If you hold every login on day one, have tested the backup in the first week and know your systems and contracts after a month, you can spend the remaining time on customers and employees.
You create the conditions for this before signing. If you want to take over a Swiss SME and would like to know what to negotiate for the handover, get in touch via our contact page for a non-binding initial conversation.
This article provides general information and does not constitute legal, tax or investment advice. For an assessment of your specific situation, please consult your fiduciary or legal advisor.




