When a tool retires, keep the connection

What we found in the news

In Microsoft's February 2025 announcement about retiring Skype (opens in a new tab), the company described a transition toward Teams and an option to export information. It introduced those arrangements with:

“During this transition period, users have a choice”

This is an earlier vendor announcement, not current migration guidance or an independent evaluation of the change. It remains a useful example of something every service should plan for: a familiar tool can close while the relationships and activities it supports still matter.

Why this matters to us

People may remember a weekly conversation more clearly than the name of the application that carries it. They know the group, the usual time and the person who helps them join. A replacement tool changes one part of that arrangement, but it can unsettle several others.

We are interested in keeping those connections recognizable through a planned closure. The work includes choosing a suitable alternative, explaining what will change and noticing who has not yet found a workable route. A successful transfer of accounts would answer only part of the question.

Find out what needs to continue

Imagine a community program learning that its video service will close. At the welcome desk, a coordinator and participant compare the old joining card with a proposed replacement. The participant's priority is simple: keeping the Friday conversation with people they know.

Begin with that purpose. Identify the activities, contacts and information people still need, then decide which replacement arrangements could support them. Some participants may want help trying another digital route. Others may prefer an ordinary telephone conversation or an in-person option the service can actually provide.

Discuss those choices before deciding that everyone should move together. Keep a clear account of what will continue, what cannot be carried across and who will help resolve questions.

Rehearse before the old route ends

A practice session can reveal differences that a feature list misses. Try the invitation on the person's actual device. Check the steps they will follow, the available communication options and whether an invited supporter can help appropriately.

Let the participant do the useful parts of the rehearsal. They might choose the contact method, open the invitation and show where they would ask for help. Update the joining instructions from what happens, rather than handing out an unchanged supplier guide.

Set a realistic period for practice while the old service is still available, where that is possible. Agree a workable fallback for the first sessions after closure. Make sure the facilitator knows which participants are using that arrangement.

Close the loose ends deliberately

A planned ending deserves an owner. Someone needs to check old invitations, saved resource links and printed cards, so they do not keep sending people to a closed door.

Review information handling with the responsible team. Confirm what must be retained, what can be transferred appropriately and how access to the old service will end. Test that necessary exported material can actually be opened before relying on it. Follow the organization's arrangements for permissions and retention.

After the move, follow up through an agreed contact route with people who wanted to continue. An absent login does not explain whether someone chose another option, met a barrier or simply missed the message.

What this means for the people you serve

People have a clearer account of how to stay involved and a say in the route they use. Families can help without becoming the default migration team. Staff can concentrate on practical exceptions because the closing date, contact arrangements and responsibilities have already been discussed.

The genus connection

The current Coaching & Mingle (opens in a new tab) experience supports configured, human-led activities with invited participants. Its setup includes room access, device needs and the formats available to the group.

When considering genus as part of a change, work through those arrangements around the activity people want to keep. Confirm which resources and connections are supported, prepare the invitation and rehearse with participants. Data transfer and any external integration need their own agreed scope. The continuing relationship gives the technical work its purpose.

One question to take away

If a familiar tool had a closing date, how would each person know their next workable way to stay involved?