Contract Radar: Planning Telecoms Renewals and PSTN Migration

The move away from the public switched telephone network (PSTN) gives telecoms resellers a dated migration programme to manage alongside ordinary contract renewals. Openreach’s published deadline is 31 January 2027. Its business migration update explains the need to prepare affected services.

SAFE CRM’s Renewals Radar helps organise the commercial side of that work by reading contract end dates from the service records you already bill. It provides a starting point for account review, rather than a complete inventory of every device or dependency affected by the switch-off.

Review Contracts in Useful Time Bands

The radar groups recorded end dates into out-of-contract, 0–30, 31–60 and 61–90-day views. Each record carries customer and recurring-value context so that the team can prioritise preparation.

An expired minimum term does not automatically mean a service has stopped or that the customer can leave without notice. Review the applicable terms and notice requirements. Equally, a service still within contract may need migration before its commercial end date.

This is why a migration review needs both the contract view and an assessment of the affected technology.

Identify Work Without an Open Renewal Deal

The coverage filter helps find records that have not yet been picked up by an open renewal opportunity. That is useful when several colleagues share a customer base and need a clear division of work.

Record the owner, the next conversation and any dependencies. An open deal shows that work has started; it does not prove that the migration is planned or that the customer has accepted an alternative.

Keep recurring values within their currency. They help prioritise commercial exposure, but should not be summed across currencies as though they were interchangeable.

Look Across Services, Numbers and Features

A reseller’s contract information can sit on several record types. The radar brings supported service, number and feature records into the review, subject to access permissions.

For migration planning, use the installed-base tools to identify products marked as legacy and examine the underlying service details. The Base Explorer capability can support that selection where enabled.

A legacy flag reflects how the product has been classified in your data. It is not an automatic technical assessment of a customer’s alarm, lift line, payment terminal or other connected equipment. Those dependencies still need checking with the relevant parties.

Carry the Agreed Renewal Into Billing

When an existing service is renewed, the workflow needs to amend the right record rather than create a duplicate charge. SAFE’s renewal process retains the link with the existing service for the billing handover.

Review the accepted price, contract term and effective date before activation. A commercial renewal and a technology migration can have different dates, so the customer communication and billing setup need to reflect the actual agreement.

Optional renewal automation can help create repeatable work where the relevant features are enabled. It does not replace the review of unusual terms or migration dependencies.

Separate Retention From New Revenue

A renewal at the existing price preserves recurring revenue. An upgrade adds value; a reduction or cancellation removes it. Keeping those outcomes separate makes the result more useful than a single total of “won” business.

For a PSTN migration programme, track service readiness and completion alongside the commercial result. A signed proposal is progress, but the affected service still needs to be moved and checked.

Prepare a Representative Review

Start with a manageable group of affected customers and verify the recorded products, contract dates and ownership. Resolve gaps before relying on a larger report.

The renewals page explains the product workflow, while quotes and proposals covers presenting the replacement offer. Contact us to review how these fit your reseller migration programme.