Swisscom BWS contract ending: plan the handover

If you have received notice that your Swisscom BWS contract is ending, first confirm the end date, the services affected and the transfer arrangements with Swisscom. The handover may cover devices, identities, e-mail and support, depending on your contract.

Plan the handover as a project: identities, e-mail, devices, network, data and backups need to be transferred with checkpoints and an agreed schedule. It is also the time to define the support model your business needs.

Preparing day-to-day support

Before choosing your next arrangement, define how support should work: who receives requests, who handles them and how urgent issues are prioritized. Ask which support windows and response times will be written into the contract.

Check how documentation and the history of previous work will be shared among the people handling your account. These records help maintain continuity, whatever the size of the provider you choose.

What has to be taken over

• Inventory: devices, users, licenses, applications, administrator access.
• Identities and e-mail: where accounts and mailboxes will live (e.g. Microsoft 365), and who administers them.
• Network: firewall, Wi-Fi, VPN, access rules, any site-to-site links.
• Data and backups: where files live, how they are backed up, how restores work.
• Timeline: a realistic switchover date, with an overlap period if possible.

Classic pitfalls

• Waiting until the last weeks: allow time for transfers, orders and testing as soon as your contract end date is known.
• Forgetting licenses and domains: who holds the subscriptions, the DNS, the tenant access?
• Not retrieving and documenting access while the current service still answers.
• Cutting the old service before testing the new one in real conditions.

How we run the takeover

At SysPros, a BWS handover starts with a documented assessment and a staged migration plan. We plan an overlap period where technical and contractual conditions allow it.

• No-obligation assessment: we document what exists before any decision.
• A staged migration plan, in the order that limits risk: e-mail, devices, network, data.
• Tested switchover: nothing is cut before the new environment is verified working.
• Documentation handed over from day one: your environment belongs to you.

Afterwards: a team that knows your environment

Once the takeover is done, day-to-day support changes in nature: your environment is documented in detail, every request is traced with a full history, and incidents are prioritized by business impact. If your file changes hands, the person taking over is fully briefed: the documentation and history follow, so you never re-explain everything from scratch.

Our support framework is built around an environment that is documented, monitored and maintained under written rules. Support windows, responsibilities and incident communication are agreed with you.