revenue - Home page(888) 815-0802
Salesforce Open CTI Sunsetting Blog Image

Salesforce Open CTI Sunsetting: Timeline, Impact, and Your Migration Options

Revenue Blog  > Salesforce Open CTI Sunsetting: Timeline, Impact, and Your Migration Options
5 min readApril 1, 2026

Salesforce Open CTI is in maintenance mode and is scheduled to retire on February 28, 2028. Salesforce’s current retirement notice says legacy connectors will no longer function at end of life. This is a migration-planning requirement, not merely a decision about whether to retain an unsupported connector.

Salesforce also documents that Open CTI is deprecated and unavailable for newly created Agentforce Service orgs. Existing customers and new-org projects therefore need different immediate checks.

Source review: October 26, 2026. See Salesforce’s Open CTI retirement notice and the Open CTI developer guide. Confirm the applicable guidance with Salesforce and your telephony provider as the transition approaches.

What is Salesforce Open CTI?

Open CTI is a browser-based JavaScript API for connecting third-party telephony with Salesforce Call Center. An implementation can expose softphone controls, screen pops, and supported record operations in Salesforce. Your telephony vendor and configuration determine the calling, recording, reporting, and other features built around that connection.

Open CTI is an integration layer, not a complete list of a vendor’s capabilities. A provider using it may also offer transcription or coaching through other components. Conversely, a product described as Salesforce-native is not automatically independent of Open CTI.

Maintenance, deprecation, and retirement are different

Stage What Salesforce currently states What your team should check
Maintenance mode No new features or enhancements are being added to Open CTI. Current dependencies, provider roadmap, and supported versions.
New-org restriction Open CTI is unavailable for newly created Agentforce Service orgs. Whether a new org or planned deployment can use the proposed integration.
Retirement: February 28, 2028 Salesforce’s retirement notice identifies end of life and says legacy connectors will no longer function. A supported replacement, validated workflow, and cutover plan before the deadline.

Do not treat the retirement date as the beginning of deprecation or assume existing connectors will keep operating indefinitely without support. Use the current Salesforce notice as the planning baseline and ask your provider how it applies to your installed configuration.

Identify the workflows that depend on the connector

Ask your Salesforce administrator and telephony provider to inventory the installed package, adapter, versions, affected orgs, and user groups. Record how each normal task works today and where its data is stored.

  • Inbound and outbound calling, click-to-dial, and softphone placement.
  • Screen pops, caller matching, transfers, routing, and voicemail.
  • Call and activity logging, dispositions, notes, and record associations.
  • Recording access, retention, historical transcripts, and permissions.
  • Automations, reports, and integrations that consume the call data.
  • Supervisor, coaching, remote, and mobile workflows your users require.

Document exceptions as well as the usual path. A successful outbound test does not establish that inbound matching, unavailable-agent routing, historical access, or downstream reporting will work after migration.

Evaluate a supported replacement

Salesforce recommends transitioning development efforts to Salesforce Voice. Evaluate its applicable editions, licenses, telephony connections, and setup against your requirements using current Salesforce guidance.

If you are evaluating another provider or a newer version of your current integration, require written confirmation of the supported architecture and its Open CTI dependencies. Ask which product, package version, org types, and licenses the proposed path requires. A generic claim of compatibility or CRM integration is not a migration plan.

For Revenue.io, explore the Salesforce dialer and request a review of your specific calling requirements. Confirm the supported migration path with the team before treating it as a replacement for your installed connector. This guide does not establish that a particular Revenue.io configuration is exempt from the retirement.

Build an acceptance-test checklist

Requirement Representative test Evidence to retain
Calling Make and receive calls using the roles and devices in scope. Observed call outcome and any unsupported workflow.
Record matching Test known, unknown, and ambiguous callers. Salesforce record association and exception-handling result.
Logging Complete calls with the required notes and outcomes. Expected fields, timing, permissions, and error recovery.
Historical access Retrieve representative older recordings and related records. Access method, retained links, permissions, and migration exceptions.
Routing and supervision Run transfers, unavailable-agent cases, and supervisor tasks. Documented behavior for the scenarios your team uses.
Downstream workflows Run reports and automations that depend on call data. Reconciled results against agreed acceptance criteria.

Confirm the required capture, transcription, coaching, and reporting capabilities separately. Moving to a new integration does not guarantee that every previous feature, recording, or automation transfers unchanged, or that every new AI feature is included.

Assign migration responsibilities before cutover

  1. Inventory: The Salesforce administrator and provider identify affected dependencies and users.
  2. Scope: Sales operations defines required tasks, while data and security owners confirm access and retention requirements.
  3. Evaluate: The project team compares written proposals, architecture, licenses, services, and ongoing ownership.
  4. Pilot: Representative users test normal and exception paths in an agreed environment.
  5. Migrate: The data owner reconciles transferred records and documents access to retained historical material.
  6. Launch: The accountable owner accepts the test evidence, trains users, and approves cutover and recovery procedures.

Set a project schedule around your dependencies rather than a universal migration-duration estimate. Compare recurring licenses and usage with implementation, training, migration, retained tools, and internal time. Use the cost-comparison worksheet to organize assumptions; obtain actual quotes before making a cost claim.

Frequently asked questions

Is February 28, 2028 a deprecation date or retirement date?

It is the scheduled retirement date in Salesforce’s current notice. Open CTI is already in maintenance mode, with separate restrictions for newly created Agentforce Service orgs.

Can our provider keep the old connector running after retirement?

Do not plan around that assumption. Salesforce’s retirement notice says legacy connectors will no longer function. Ask your provider for a documented supported replacement and how it applies to your exact configuration.

Will recordings and Salesforce activities move automatically?

Do not assume they will. Agree ownership, retention, permissions, export/import scope, and a reconciliation process. Test historical access as a separate acceptance requirement.

Does Salesforce-native mean unaffected?

No. The label does not establish the underlying integration architecture. Confirm the dependencies, applicable org types, package versions, and provider migration plan.

Discuss your Salesforce calling workflow with Revenue.io and bring the dependency inventory and acceptance checklist to the conversation. Validate architecture before comparing optional capabilities or making a purchase.

Categories: