The mapping table you put in the migration pack

About five minutes of reading

Names from the old platform are not Connect resources. Write the map before you build the queues.

A CUCM calling search space is not a routing profile, but the profile is the closest idea of 'who can receive what'. A partition is not a Connect object. A UCCX CSQ and a UCCE skill group map to a queue. Precision steps map to routing criteria. A script, an Architect flow, and an Avaya vector map to a contact flow.

Finesse maps to the CCP or a Streams desktop. CUIC maps to real-time metrics, historical metrics, and the CTR. A recording trunk maps to the recording block and S3.

• Write one row per old object, with the Connect object and the pitfall.
• Skills can become proficiencies or extra queues. Pick one and say why.
• Hunt pilots become queues plus priority and delay.
• The lab translator does this row by row.

Number on this page: Platforms 6. CUCM, UCCX, UCCE, Webex CC, Genesys, Avaya

Different names. Write the pitfall in the third column.

1. Inventory. Old objects.
2. Map. One row each.
3. Pitfall. What will not survive.
4. Build. Only the Connect column.

What usually goes wrong: Creating a queue named after every CUCM partition.

How Connect Customer uses routing profiles - Amazon Connect Customer AWS docs. last checked 2026-10

The prose is a study paraphrase. The link is the source of the facts.

Glossary

• Calling search space CUCM's list of partitions a phone may dial. The Connect cousin is a routing profile, and they do not configure each other.
• CSQ A UCCX contact service queue. Map it to a Connect queue, not to a routing profile.
• Precision queue A UCCE queue with attribute steps. Map the steps to routing criteria, not to one flat skill group.
• Finesse The Cisco agent desktop. The Connect cousins are the CCP, the agent workspace, and a Streams application.

Mind map

Open the Bridge mind map

Sister technologies

Migrations fail when a skill group, a script, and a Finesse gadget are all called 'the queue'.

Config and troubleshooting

Creating a queue named after every CUCM partition.

CUCM, UCCX, and UCCE have no CloudFormation resource in this API. The objects you create on the Connect side are the queue, the routing profile, and the hours. Map the old skill group onto those, not onto a single queue name.

Queue RoutingProfile

Resources:
  MigratedQueue:
    Type: AWS::Connect::Queue
    Properties:
      InstanceArn: !GetAtt CampusInstance.Arn
      Name: BillingSkill
      HoursOfOperationArn: !GetAtt OfficeHours.HoursOfOperationArn
      Description: Was a UCCE skill group. Priority now lives on the routing profile.

Integration map

Join records on ContactId. The integration map room lists the seams.

Cross-platform bridges

A CUCM calling search space is not a routing profile, but the profile is the closest idea of 'who can receive what'. A partition is not a Connect object. A UCCX CSQ and a UCCE skill group map to a queue. Precision steps map to routing criteria. A script, an Architect flow, and an Avaya vector map to a contact flow.

Open the mapping room

Future hooks

Hooks you can adopt later: EventBridge contact events, the CTR stream, agent events, Kinesis Video, Customer Profiles events, Cases, Show view, data tables, External Tool, and the flow language JSON in your pipeline. Live Sync and Agentic CX are the 2026 hooks for guided and agentic experiences.