Open CTI & Salesforce Voice

The Open CTI migration checklist: 15 things to assess before you start

RocketCX ·

A white checklist with fifteen boxes sits beside a purple telephone handset and a cable junction, representing the dependencies to assess before an Open CTI migration.

Before migrating from Open CTI, assess your adapter, custom code, users, replacement platform, licences, phone numbers, routing, presence, screen pops, call logging, recordings, reporting, network, testing and cutover.

For each area, record what exists, what must change, who owns it and how you will verify the replacement.

Salesforce has scheduled Open CTI retirement for 28 February 2028. Its official notice says Open CTI implementations will no longer function after that date.

The checklist below is RocketCX’s recommended assessment structure, informed by Salesforce documentation. It defines the evidence needed to scope a migration, rather than prescribing one configuration for every organisation.

1. Inventory your current adapter

Record the telephony provider, installed package, version, Salesforce Call Center definitions and apps containing the softphone. Identify active deployments separately from unused configuration. Assign a technical owner who can explain how Salesforce connects to the phone platform.

2. Find custom Open CTI dependencies

Inspect adapter code, Visualforce pages, Lightning components and external integrations for dependencies on Open CTI. Record each dependency’s purpose and owner. Decide whether to replace, rebuild or retire it; do not assume installing a new package reproduces custom behaviour.

3. Map users, identity and permissions

List agents, supervisors, administrators and integration users. Document sign-in, user provisioning and access to call records and recordings. Establish how Salesforce identities map to telephony users, including joiners, leavers and users working across multiple teams.

4. Confirm the replacement is supported

Name the exact telephony model, connector and package version. For partner telephony, Salesforce recommends confirming a generally available, supported package before production cutover. Check country coverage, supported regions and purchasing eligibility for your organisation, rather than assuming a US offering applies in the UK.

5. Establish licences and complete costs

Check the supported Salesforce editions and obtain a written licence breakdown. Separate Salesforce subscriptions, provider charges, usage, implementation and optional AI. Include contract overlap and test environments in the budget. Published per-user pricing is not the full migration cost.

6. Verify your phone-number plan

Inventory numbers, number types, carriers, account holders and contractual commitments. Determine which numbers stay, need forwarding or require porting. Confirm eligibility and lead times with the receiving provider. For Amazon Connect, AWS documents number-specific portability restrictions.

7. Document routing and IVR behaviour

Capture opening hours, holidays, queue rules, skills, overflow, callbacks, voicemail and escalation paths. Include exceptions such as unanswered transfers. Decide which system will own each routing decision, and turn business-critical journeys into test cases before redesigning them.

8. Assess agent presence and capacity

Document what each agent status means and how availability changes during calls, wrap-up and digital work. Identify where Salesforce and telephony statuses synchronise. Define expected behaviour when one system disconnects or an agent signs in through multiple interfaces.

9. Specify screen pops and customer matching

Record which objects and fields identify the caller. Define outcomes for withheld numbers, duplicate matches, unknown callers and transferred calls. Include international number formats. Use representative records to prove that the proposed matching logic opens the correct information.

10. Trace call logging and downstream automation

Identify whether current logging writes Tasks, custom objects or other records. Map fields and relationships to the proposed record model. Trace Flows, Apex, integrations and follow-up processes triggered by those records. Check how retries and duplicate events should behave.

11. Plan recording and historical-data access

Establish where recordings and transcripts reside, who can access them and what happens when the current contract ends. Agree retention, export and retrieval requirements with the relevant owners. Test access to historical calls separately from recording new calls.

12. Preserve useful reporting

List operational dashboards and define their metrics, including missed calls, transfers, handling time and wrap-up. Identify the replacement data sources and reconcile sample results. Decide how users will compare periods spanning the migration when old and new records differ.

13. Check network, devices and service limits

Assess office, home-working, VPN and virtual-desktop environments. Test browser audio permissions, headsets and connectivity using the chosen provider’s guidance. Verify expected concurrent calls and relevant quotas. Salesforce’s network guidance distinguishes Salesforce connectivity from the telephony provider’s requirements.

14. Define environments and acceptance tests

Confirm which sandbox and telephony test environments your route supports. Plan test numbers and representative data. Assign business owners to approve inbound calls, outbound calls, transfers, matching, logging and failure scenarios. Set measurable acceptance criteria before the pilot begins.

15. Agree rollout, contingency and support ownership

Define pilot users, deployment stages, supplier activities and go/no-go authority. Document what can be reversed and what cannot, particularly around number porting. Assign monitoring and escalation owners. Retire the old configuration only after validating the replacement and required historical access.

What should the assessment produce?

Bring the findings together in an agreed scope containing:

  • The current configuration and its dependencies.
  • The proposed architecture and confirmed supplier support.
  • Requirements, gaps, costs and named owners.
  • Acceptance tests and a rollout approach.
  • Unresolved decisions that could change the budget or delivery date.

For the wider process, read our Open CTI migration guide.

If you need help establishing the scope, explore RocketCX’s Open CTI to Salesforce Voice migration service.

Official references

Sources checked: 16 November 2026