Blocker 02 · Solutions

Leaving your current contact center platform feels too risky: a phased migration to Amazon Connect

Nobody wants to be the person who switched off the phones. A phased migration lets you move one group at a time, with the old platform still running, so every step is small and every step can be tested.

2–4 weeksTypical time to port US or Canada numbers once portability is verified and documents are submitted. Outside the US and Canada, plan for two to six months.Source: AWS, phone number porting documentation

Illustration. The blocker: Moving off the old platform feels too risky. The fix: A phased move, one group at a time.

The blocker

The contact center runs on a legacy on-premises system. The hardware is aging, the support contract renewal is coming, and leadership likes the idea of Amazon Connect. But every time the project is discussed, the same fear stops it: what if we switch over and the phones stop working?

That fear is reasonable when the plan is a single weekend cutover. Hundreds of agents, every IVR, every phone number and every integration all change at once. If something breaks, everything breaks. The risk is not in Amazon Connect. It is in moving everything in one step.

Why it happens

  • Big-bang plans. All lines of business move on the same night, so there is no small, safe first step to learn from.
  • No way to run both platforms. Without a plan for calls that cross platforms, teams assume they cannot run old and new side by side.
  • Numbers are treated as an afterthought. Porting has lead times set by carriers and regulators, and it is often left until the last weeks.
  • Testing on live traffic. New flows are first exercised by real customers on the day of cutover.

How Amazon Connect solves it

AWS documents several ways to move in phases. The common idea is simple: build and test on Amazon Connect while the old platform keeps serving customers, then move one group at a time.

1. Pick a migration pattern, not a cutover date

In Scenario and deployment approaches, AWS describes the options:

  • New workload first. Start with something that is not on the legacy platform today, to build skills and confidence.
  • IVR first. Amazon Connect flows handle self-service and routing, and transfer callers to agents still on the legacy platform.
  • IVR last. The legacy IVR stays in place and transfers callers to agents already on Amazon Connect.
  • Line of business or site. Move one business unit, site or agent group at a time.

Whichever you choose, the legacy platform and Amazon Connect run side by side until the last group has moved. Decide early whether one instance or several fits you. AWS generally recommends a single instance unless there are strong regulatory, data or geographic reasons for more.

2. Run both platforms in parallel

When calls need to move between platforms with their context, AWS calls this a hybrid architecture. You claim as many phone numbers as your expected maximum concurrent contacts, and keep an intermediary database both platforms can read. Before a transfer, the sending platform picks a free number, marks it in use and writes the contact details. On the Amazon Connect side, a Lambda function does this work. The receiving platform looks up the details by that number, routes the call, and frees the number again. AWS notes this is usually an interim step because of the extra cost and complexity, which is exactly how it should be used.

3. Test every flow before a real customer hears it

You can create an Amazon Connect instance and claim a DID or toll-free number for testing. AWS recommends this in Verify flows before porting numbers: test your flows on a claimed number before the porting date, then release it.

Legacy call flows are rebuilt in the Amazon Connect flow designer. Once built, they move between development and production with flow import and export (flows under 200 blocks and 1 MB) or, for hundreds of flows, the APIs described in Migrate flows. That page has one detail worth knowing: you must map every queue, flow and prompt ARN from the source instance to the target, or the update fails.

4. Port numbers by group, on a schedule you planned

Customers keep dialing the numbers they know. Porting moves them from your carrier to Amazon Connect. AWS is clear about the timing:

  • US and Canada numbers typically take two to four weeks after portability is verified. Elsewhere, two to six months.
  • US DID and toll-free porting requests cannot be submitted more than 30 days before the porting date.
  • Requests for more than 10 distinct number ranges or locations are treated as a project that needs coordination with your AWS account team.
  • Most porting activity completes in 15 to 30 minutes, with possible call disruption, usually during the losing carrier’s business hours.

The porting process asks for the exact flow each number should map to. About three to four days before the porting date, AWS loads the numbers into your instance, and you attach each number to its flow yourself, so it is ready to take calls when the port completes.

5. Cut over by group

Each group follows the same steps: flows tested, agents trained, numbers ported, then live. AWS gives the example of an internal service desk as the first line of business to move. Once it is stable, the next group goes, and the hybrid layer shrinks until it can be removed.

What good looks like

Each wave is small enough to roll back. The first customers to reach Amazon Connect hear flows that were tested weeks earlier. Calls that cross platforms carry their context, so callers do not repeat themselves. Porting dates are in the plan from day one, not discovered in the last month. When the last group moves, the legacy platform is switched off on a normal working day.

Where to start

  1. List your lines of business, sites and phone numbers, and note which carrier and country each number sits with.
  2. Choose a pattern and a low-risk first group.
  3. Build that group’s flows in Amazon Connect and test them on claimed numbers.
  4. Open the porting request for the first group’s numbers as soon as the go-live window is known.
High-level architectureParallel run with cutover by group
Customer
  • Phone call
  • Existing numbers
Legacy platform
  • Legacy IVR
  • Legacy queues
  • Legacy agents
Amazon Connect
  • Claimed test numbers
  • Flows
  • Queues
  • Routing profiles
Hybrid transfer
  • Lambda lookup
  • Shared contact data
  • Transfer numbers
Migrated agents
  • Agent workspace
  • First group live
Reporting
  • Real-time metrics
  • Historical metrics
  • People
  • Your systems
  • Amazon Connect
  • Built by Digiclarity
  • AWS services
  1. Flows, queues and routing profiles are built in a new Amazon Connect instance and tested on claimed DID or toll-free numbers, while every live call still lands on the legacy platform.
  2. The first group goes live. The legacy IVR transfers its calls to Amazon Connect, or Amazon Connect answers and transfers the rest back, depending on whether you go IVR first or IVR last.
  3. When a call crosses platforms, the sending side writes the contact details to a shared store keyed by a free transfer number. The receiving side reads them (on Amazon Connect, with a Lambda function), so the caller does not repeat themselves.
  4. Once the group is stable, the numbers it owns are ported to Amazon Connect and attached to the tested flows in a planned porting window.
  5. Real-time and historical metrics for each migrated group show whether it is ready to hand over the next one. The hybrid layer is removed after the last group moves.
References

Official AWS documentation

Every Amazon Connect capability in this post links to AWS’s own documentation, so you can check the details for your Region and account.

  1. Scenario and deployment approachesdocs.aws.amazon.com
  2. Single instance or multiple instances?docs.aws.amazon.com
  3. Create an Amazon Connect instancedocs.aws.amazon.com
  4. Get a local toll-free or DID phone numberdocs.aws.amazon.com
  5. Verify flows before porting numbersdocs.aws.amazon.com
  6. Migrate flows to an instance, Region, or environmentdocs.aws.amazon.com
  7. Import and export flows between flow designersdocs.aws.amazon.com
  8. What does it mean to port phone numbers?docs.aws.amazon.com
  9. How to port your numbersdocs.aws.amazon.com
  10. How long does it take to port phone numbers?docs.aws.amazon.com
  11. Attach a claimed or ported phone number to a flowdocs.aws.amazon.com
Start here

Tell us what you want to improve.

We will tell you whether a voice agent fits it, what it would take, and what it should return. You will hear back within a week.

  • AWS Advanced Tier Services Partner
  • AWS Migration Services Competency
  • Amazon Connect Delivery Partner
  • AWS AI Services Competency
  • AWS Experience-Based Acceleration (EBA) partner
  • ISO/IEC 27001 certified
  • SOC 2 Type II
Certified supplierMWDBE certifiedTexas HUB certifiedNCTRCA certified
+1 (214) 550-14936275 West Plano Parkway, Suite 500, Plano, Texas 75093