Skip to content

Migration guide · Customer Service

Open CTI to Service Cloud Voice migration

Open CTI softphone integrationsSalesforce Service Cloud Voice or partner telephony

Short answer

As Salesforce moves away from older Open CTI telephony approaches, contact centres need to move to Service Cloud Voice (with Amazon Connect or partner telephony) or a supported partner integration, keeping call logging, routing and screen pops working.

Why firms make this move

Open CTI connected many phone systems to Salesforce. Salesforce now steers customers to Service Cloud Voice, which brings calls, transcripts and AI into the agent console, and to partner telephony options (bring your own telephony). Firms should check Salesforce's current timelines and plan the move with their telephony vendor.

What moves

  • Softphone and call logging
  • Routing and queues (Omni-Channel)
  • Screen pops and caller identification
  • Recordings and transcripts

How the data maps

FromTo
Open CTI softphoneService Cloud Voice or partner telephony in the console
Vendor routingOmni-Channel unified routing
Manual call notesTranscripts and AI summaries

See the field-by-field map ↓

What to watch out for

  • Telephony vendor support for Service Cloud Voice
  • Licence costs
  • Recording consent and retention
  • Agent retraining

How Vantage Point runs the migration

  1. Review current telephony and vendor options
  2. Choose Amazon Connect or partner telephony
  3. Configure Service Cloud Voice and routing
  4. Pilot with one team
  5. Roll out and decommission Open CTI

Typical timeline

Typically 4 to 10 weeks.

Frequently asked questions

Do we have to switch phone vendors?

Not necessarily. Many telephony vendors support Service Cloud Voice through partner telephony.

What do agents gain?

Calls, transcripts and AI summaries inside the console, with unified routing.

Last reviewed October 2, 2026 by the Vantage Point team. Browse all migration paths →

Field-level map

Open CTI to Service Cloud Voice: field by field

5 mappings we start from on this migration, 5 of which need a transform, a lookup or a decision. Every project gets its own signed-off version; this is the baseline.

FromToHowNotes
Open CTI softphoneSoftphone layout Service Cloud Voice / partner telephonyOmni-Channel voice req rebuild
Call log taskTask (call) Voice Call record— derive Voice Call records hold recording, transcript and duration.
Screen-pop logicCaller lookup Omni-Channel flow / screen pop— rebuild
Routing in telephonyQueues / skills Omni-Channel routingQueues / skills rebuild
RecordingsCall recordings Voice Call recording / partner storage— manual review

Field names are the platforms' standard API names; your org's custom fields are mapped during discovery. What the "How" labels mean

How labels
direct
Value copies across unchanged.
picklist map
Each source value is mapped to a target value.
lookup
Matched to an existing record, such as a user by email.
association
Becomes a relationship between records, loaded in a later pass.
derive
Calculated or cleaned during the load.
split / concat
One field becomes several, or several become one.
rebuild
Configuration or automation that is rebuilt rather than moved.
drop
Not migrated, deliberately.
manual review
Needs a decision with your team before the load.