---
schema_version: "1"
id: 1abb032e1f7cad8cbfb8f9c341f76acb450f9565d01ea6cb91503c819047ad39
title: Migrate Your Open CTI Integration to Salesforce Voice with Partner Telephony
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/service-cloud/api-cti/guides/migrate-cti.md
canonical_url: https://developer.salesforce.com/docs/service/api-cti/guide/migrate-cti.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 8876dd6109f1b48f1fc993b78b2e17bd7ad9ed693e11145f2e6d3948689669b9
products:
  - Open CTI Developer Guide
  - Service Cloud Developer Content
---

# Migrate Your Open CTI Integration to Salesforce Voice with Partner Telephony

Move your existing Open CTI integration to a Voice implementation by using planning resources, conceptual comparisons, step-by-step migration tasks, and troubleshooting guidance.

This guide is for partners and independent software vendors migrating an existing Open CTI (Lightning) package to a Salesforce Voice with Partner Telephony connector built on Partner Telephony. For Salesforce admins moving from Open CTI to Salesforce Voice with Partner Telephony, see the [Migrate from Open CTI](https://help.salesforce.com/s/articleView?id=service.cti_migrate_map.htm) learning map in Salesforce Help.

**important:** Open CTI is in maintenance mode and is scheduled for retirement in February 2028. No new features or enhancements are being added to Open CTI. Effective immediately, Open CTI is deprecated and unavailable for newly created Agentforce Service orgs. To ensure long-term compatibility and access to the latest innovations, we recommend transitioning your development efforts to Salesforce Voice. For more information, see this [Knowledge Article](https://help.salesforce.com/s/articleView?id=005306437&type=1), [learning map](https://help.salesforce.com/s/articleView?id=service.cti_migrate_map.htm), and [developer migration guide](/docs/service/api-cti/guide/migrate-cti.html).


- **[Plan Your Migration](https://developer.salesforce.com/docs/service/api-cti/guide/plan-cti-migration.md)**  
   Use the migration checklist and key resources to plan your move from Open CTI to Salesforce Voice with Partner Telephony.
- **[Compare the Conceptual Models of Open CTI and Salesforce Voice with Partner Telephony](https://developer.salesforce.com/docs/service/api-cti/guide/compare-opencti-voice.md)**
  Understand the architectural and data model differences between Open CTI and Salesforce Voice with Partner Telephony, including the shift from Task records to VoiceCall records.
- **[Clone Before You Build](https://developer.salesforce.com/docs/service/api-cti/guide/clone-before-build.md)**  
   Start your migration from the demo connector rather than building from scratch.
- **[Build Your Connector](https://developer.salesforce.com/docs/service/api-cti/guide/build-connector.md)**  
   Replace Open CTI adapter logic with Salesforce Voice with Partner Telephony connector methods and events, starting from the demo connector.
- **[Migrate the Single Call Flow](https://developer.salesforce.com/docs/service/api-cti/guide/migrate-single-call.md)**
  For the most common case, one inbound call, accepted, connected, and ended, this is the connector contract.
- **[Migrate Multiparty and Transfer Calls](https://developer.salesforce.com/docs/service/api-cti/guide/migrate-multiparty-transfer.md)**
  Salesforce Voice with Partner Telephony supports four multiparty patterns.
- **[Migrate Custom UI Integration](https://developer.salesforce.com/docs/service/api-cti/guide/custom-ui-integration.md)**  
   Replace Open CTI iframe-based UI patterns with Voice Extensions, Voice Toolkit, and LMS.
- **[Migrate Screen Pop](https://developer.salesforce.com/docs/service/api-cti/guide/migrate-screen-pop.md)**  
   Replace the Open CTI screen pop pattern with an Omni-Channel flow screen pop action.
- **[Migrate Rep Presence Status](https://developer.salesforce.com/docs/service/api-cti/guide/migrate-presence-status.md)**  
   Manage rep presence through Omni-Channel instead of your previous Open CTI pattern.
- **[Migrate Supervisor Features](https://developer.salesforce.com/docs/service/api-cti/guide/migrate-supervisor.md)**  
   Replace custom-built Open CTI supervisor features with built-in Salesforce Voice with Partner Telephony connector methods.
- **[Migrate Reporting](https://developer.salesforce.com/docs/service/api-cti/guide/migrate-reporting.md)**  
   Use VoiceCall as the primary reporting object in Salesforce Voice with Partner Telephony.
- **[Address Migration Roadblocks](https://developer.salesforce.com/docs/service/api-cti/guide/troubleshoot-migration.md)**  
   Learn about common migration roadblocks and how to address them.