Onboarding
Ownership and Handover
Qualifying customer-specific custom IP ownership starts in subscription month 13. Understand year-two choices, dependencies and a departure handoff.
Ownership of qualifying customer-specific custom IP starts in month 13 of your subscription. The trigger is the subscription month, not the date a build finishes.
Ownership and handoff are different
Ownership describes the qualifying custom work that becomes yours. A handoff is the practical process of transferring the agreed work and information needed for another team or provider to take over.
The exact transferable assets, retained CNX platform components, third-party licenses and dependencies, and handoff process need to be agreed. Custom work is not a promise that every shared platform component or third-party service becomes yours.
Your choices in year two
- Continue: the same plan stays at the same price.
- Choose a lower plan: agree the support that will continue and the services that will change.
- Leave: take your transferable work through the agreed handoff process. CNX maintenance ends on departure.
Ownership does not require departure, and a support change does not reset the ownership trigger. There is no automatic price reduction at month 13.
Prepare for a departure
Before leaving, ask CNX to confirm:
- The inventory of qualifying custom work and what transfers.
- The platform and third-party dependencies that remain.
- Accounts, access, documentation and ongoing costs needed for operation.
- Who will take over maintenance and how the handoff will happen.
Confirm timing and any unresolved details for your engagement. This guide does not promise that every asset runs independently, a fixed handoff deadline or a particular migration method.
Before month 13
If you are considering an earlier departure, ask about the applicable early-exit terms before deciding. Ownership starting in month 13 does not establish an earlier transfer policy.