How to Change Your Genesys Partner of Record
You picked Genesys Cloud. You did not pick your partner for life.
Customers change their Genesys partner of record every year. Most wait too long because they assume switching means a full reimplementation. It does not. Your platform stays. Your configuration stays. What changes is who supports it.
The short answer: To change your Genesys partner of record, choose your new partner, notify your Genesys account team, time the switch to your renewal, grant the new partner access through authorized organization pairing, complete knowledge transfer, then remove the old partner's access. Your Genesys Cloud configuration and data stay in place.
What Genesys partner of record means
Three things get confused when people talk about their partner:
Who holds the relationship. The partner Genesys recognizes on your account. [Verify: what partner of record controls, such as billing, renewals, and support routing.]
Who does the work. The engineers who configure, change, and fix your environment.
Who you call. The first line when something breaks.
In a healthy partnership, one company does all three well. When you change partner of record, all three move.
Your Genesys contract and your partner contract are separate
Most customers have two agreements.
Your Genesys agreement covers your licenses and subscription term.
Your partner agreement covers implementation, support, and managed services.
This matters. Changing partners does not end your Genesys subscription. Your license commitment runs on its own terms. Your partner agreement includes exit terms, including notice periods and whether you can end services without cause.
Read both before you start. Partners cannot change the Genesys agreement for you, so do not expect a new partner to renegotiate your license terms as part of the switch.
Signs it is time to switch Genesys partners
Your tickets go to a queue instead of a named person.
Business reviews stopped, or never started.
Simple changes come back as project quotes.
No one can explain why your routing was built the way it was.
Genesys ships features, and nobody tells you which ones matter.
If this sounds familiar, read Your Genesys Partner Disappeared After Go Live first. Sometimes the fix is a conversation, not a switch.
What you keep when you change Genesys partners
You keep
Your Genesys Cloud organization
Your flows, queues, skills, and routing
Your users, roles, and permissions
Your data, recordings, and reporting history
Your phone numbers and licenses
You put at risk
Knowledge that lives in your old partner's heads
Customizations nobody documented
Integrations or middleware your old partner hosts outside your org
Credentials, API keys, or OAuth clients tied to your old partner
Anything billed through your old partner rather than directly
The first list is safe. The second list is where transitions go wrong. Build your plan around it.
How to change your Genesys partner of record in six steps
1. Choose your new Genesys partner. Do this before you notify anyone. Use the ten questions below.
2. Notify your Genesys account team. [Verify: who submits the partner-of-record change, what form or approval is required, and how long Genesys takes to process it.]
3. Set your timing. [Verify: whether a change can happen mid-term, and how billing transfers when it does.] Renewal is almost always the cleanest window.
4. Grant access to the new partner. Partners work in your environment through authorized organization pairing. You approve the new partner's pairing request, then assign roles to their users and groups. Many customers give their partner the Admin or Master Admin role. Genesys limits each organization to 25 authorized users, and you can remove access at any time. See the Genesys Resource Center article Authorize users and groups to work in your organization for the exact steps.
5. Run knowledge transfer while both partners have access. Do not remove your old partner until the handoff is complete. Use the checklist below.
6. Cut over support. Move ticket routing, escalation paths, and after-hours coverage to the new partner on a set date. Then remove the old partner's access. Own that step yourself.
[Add a realistic timeline range from start to finish.]
Why renewal is the best time to switch
You are already reviewing terms and pricing.
Your partner agreement is likely up for renewal too.
Genesys expects account changes at renewal.
You can pair the switch with a fresh roadmap instead of a rescue.
Start the conversation 90 to 120 days before your renewal date. Waiting until the last month forces rushed decisions.
Ten questions to ask your new Genesys partner
Who owns my account after the transition? Give me a name.
Are the engineers who assess my environment the same ones who support it?
Are your engineers full-time employees based in the US?
What does your first 90 days look like?
How do you run knowledge transfer from an outgoing partner?
What happens if my old partner does not cooperate?
What is included in support, and what is billed as a project?
How often do we meet, and what do we review?
How do you handle Genesys releases that affect my environment?
Can I talk to a customer who switched to you from another partner?
Question ten is the one most partners avoid. Ask it anyway.
Knowledge transfer checklist
Get these documented before your old partner loses access:
Architect flows, with the reasoning behind complex logic
Queues, skills, languages, and routing rules
Scripts and data actions
Integrations, including where each one is hosted and who owns the credentials
OAuth clients and API keys
Outbound campaigns, contact lists, and rule sets
Workforce management configuration
Custom reports and dashboards
Escalation paths and open tickets with Genesys
Known issues and workarounds
If your old partner hosts anything outside your org, get a plan for it in writing. That item is most likely to break on cutover day.
What a bad partner transition looks like
Old partner access removed before documentation is complete
An integration goes down because it ran on the old partner's server
Nobody knows who to call during the first outage
The new partner spends the first 60 days discovering what should have been handed over.
Every one of these is preventable with the checklist and a firm cutover date.
Frequently asked questions
Do I have to reimplement Genesys Cloud to change partners? No. Your organization, configuration, and data stay in place. The new partner takes over support of what you already have.
Does changing partners affect my Genesys contract? Your Genesys subscription and your partner agreement are separate. Changing partners does not end your license term.
When is the best time to change Genesys partners? At renewal. Start the process 90 to 120 days before your renewal date.
What if my current Genesys partner will not cooperate? You control access to your own organization. Document everything you can, grant access to your new partner, and involve your Genesys account team early.
How long does a Genesys partner of record change take? [Add range once confirmed.]
About VDS
VDS is a Genesys Elite Partner focused only on Genesys Cloud. We help customers switch partners without starting over, and we stay after the transition. Talk to a VDS expert about your renewal.
About the author
Nick Glimsdahl is Director of Contact Center Solutions at VDS, a Genesys Elite Partner focused only on Genesys Cloud.