In 2026, the operational task around Softphone CTI Adapter is migration off it, not new deployment. Browser plugin support is gone, vendor maintenance is in maintenance-only mode, and the user experience degrades on every browser upgrade. The migration path goes to Open CTI in most cases, or to Service Cloud Voice for greenfield contact center work. This guide covers the Open CTI migration, which is the higher-effort and higher-impact path that most existing Salesforce orgs running the Adapter need to follow over the next 12 to 24 months.
- Inventory the existing Softphone CTI Adapter deployment
Document the current state: which phone vendor (Cisco, Avaya, Genesys, Mitel, other), how many users have the Adapter installed, which Salesforce Lightning or Classic UI is in use, which custom Apex or Visualforce code depends on the Adapter, and what custom screen-pop logic the team relies on. Capture the current call volume and the SLA the contact center operates under. The inventory is the source of truth for the migration scope; without it, you cannot estimate the rework effort or set a realistic timeline. Share the inventory with the phone vendor account team so they can scope their side of the project.
- Engage the phone vendor for the Open CTI package
Contact the phone vendor and confirm they have an Open CTI implementation available on AppExchange. For tier-one vendors (Cisco, Genesys, Avaya, Mitel, Five9, NICE), this is a yes. For smaller or specialized vendors, you may need to push them to publish, or migrate to a different vendor that already has Open CTI. Get the vendor to commit to a migration plan: their package version, the user provisioning steps on their side, the supported Salesforce editions, and the expected migration window. Document the plan with named owners on both sides; vendor migrations stall without explicit ownership.
- Install Open CTI in sandbox and migrate custom logic
In a sandbox refreshed from production, install the vendor Open CTI AppExchange package. Configure the Call Center record in Setup, including the SCV-XML configuration the vendor publishes. Assign a pilot user group to the new Call Center. Migrate any custom Apex logic that depended on the old Adapter to use Open CTI hooks instead: screen pop customizations move from the Adapter pop logic to the Lightning component lifecycle hooks; call logging customizations move to the Open CTI logging API; custom telephony fields stay in place if the field references the standard Call object. Test thoroughly with the pilot users for two weeks before promoting.
- Roll out, decommission, and document
Roll out Open CTI to production users in waves: pilot for two weeks, then 25 percent of users for one week, then 50 percent, then full population. After each wave, monitor call volume, screen pop success rate, and user-reported issues. Once the full population is on Open CTI, deactivate the old Softphone CTI Adapter Call Center, document the rollback path (in case of unexpected issues), and remove the Adapter desktop installer from the IT software catalog. Update the org telephony runbook and the user training materials. Set a date in three months to validate the migration is sticking; users sometimes regress to old behaviors when frustrated.
- Browser plugin support is gone. Modern browsers (Chrome, Edge, Firefox, Safari) all dropped NPAPI and ActiveX. Softphone CTI Adapters that depend on plugins do not work on current browsers; users may be running degraded older browsers.
- Open CTI is a vendor-coordinated migration. Without an Open CTI package from your phone vendor, you cannot migrate. Smaller vendors may not have shipped one; verify availability before committing to the timeline.
- Custom Apex and Lightning code that called Adapter-specific APIs has to be rewritten to use Open CTI hooks. Estimate this rework explicitly during the inventory step; surprise rework derails the project.
- User-side Adapter installation requires admin rights on the desktop. Removing the Adapter at decommission time also requires admin rights. Coordinate with IT to push the removal through the standard software management tools.
- Service Cloud Voice is the strategic Salesforce direction for new contact centers. Evaluate it as an alternative to Open CTI for greenfield projects; Open CTI is the right answer only when the customer wants to keep an existing phone vendor relationship.