Transition to the AgentExchange Go-To-Market (GTM) app to modernize your selling lifecycle and move away from manual processes toward a unified, automated experience. By migrating existing Channel Order app (COA) customers to the GTM app, partners can significantly reduce operational overhead through automated provisioning, payment collection, and payouts. As you begin transitioning customers to the GTM app, keep these considerations in mind.
Net-new orders that meet requirements must be conducted through the GTM app.
Net-new is product-level, not partner-level: Partners can sell to existing customers via the GTM app as long as it’s a net-new product that the customer hasn’t purchased before.
Example: If a customer purchased App A offline, with the partner submitting an order through COA, the customer can buy App B through the AgentExchange GTM app.
Offline contracts can’t be expanded through the GTM app: If a customer purchased app A offline, with the order submitted through COA, they can’t add more app A licenses in the GTM app during an active contract period. Extra licenses for that subscription must be processed through the original offline channel. After the contract expiration date, the customer can migrate to the GTM app.
Add-ons are only supported for GTM app purchases: After a customer purchases a product in the GTM app, they can expand that subscription in the GTM app with add-ons. Add-ons can include extra licenses and new products. You can’t extend purchases made offline via the GTM app until you migrate the contract.
Contracted apps only: Partners can only sell apps they’re contracted to transact through the AgentExchange GTM app. Not all apps in a partner’s portfolio may be eligible.
Use this table to determine whether your desired application migration process is possible.
| Customer Status | Original Purchase Type | Application Migration Process | Purchase Type in GTM App | Supported in GTM App |
|---|---|---|---|---|
| Net-new customer | Initial order through GTM app | New contracted app in GTM* | Initial purchase | Supported |
| Existing customer | Purchased offline, order submitted via COA | Cancel existing COA contract and create app contract in GTM | Initial purchase | Supported |
| Existing customer | Purchased offline, order submitted via COA | Keep existing COA contract and add new licenses in GTM | Add-on | Not supported |
| Existing customer | Purchased offline, order submitted via COA | Keep existing COA app and migrate to GTM upon contract renewal | Migrate to GTM with a new service order at the time of renewal | Supported |
| Existing GTM customer | Purchased in GTM | Keep existing GTM order and add extra licenses | Add-on (additional licenses) | Supported |
| Existing GTM customer | Purchased in GTM | Keep existing GTM order and add additional products | Add-on (new product) | Supported |
*Contracted app: Any app the partner is contracted to sell through the AgentExchange GTM app.
Move an existing Channel Order App (COA) customer to the GTM App before they renew their Partner Application contract. You can’t use the GTM App to distribute the same application to a customer until their active COA service order and licenses expire.
Cancel the COA order.
From your PBO, go to the COA.
Submit a cancellation order for the customer’s active service order in the Channel Order App. Cancellations must be done at least 7 days before the renewal date.
For more information about canceling a contract, see Channel Order Application FAQ—Order Accuracy & Tracking.
Go to the GTM app.
Create a customer record.
Create an initial offer.
After your cancellation order in COA has activated, create and send an offer to the customer.
Set the service start date.
To make sure that your customers don’t experience a lapse in their licenses, set the service start date to match the the expiration date of the service order you canceled in step one.
Important
j
