CPQ migration team: five roles, their time by week, and when you need a partner
A CPQ migration needs five roles, not five people: an executive sponsor who owns the date, a project lead who owns the inventory and the difference log, a Salesforce admin who owns the org, a sales-ops owner who owns pricing and templates, and two or three reps who quote real deals in the parallel run. Total internal effort for a 4–8 week Kugamon move is roughly 120–200 hours. A Revenue Cloud Advanced rebuild is a 12–18 month project in practice and needs a correspondingly larger team.
The five roles
| Role | Owns | Decides | Typical person |
|---|---|---|---|
| Executive sponsor | The date, the budget, the scope line. | Migrate vs stay; cutover date after parallel run passes. | CRO, CFO or COO |
| Project lead | Inventory, plan, difference log, vendor relationship. | Migrate / rebuild / archive per object; quote-history cutoff. | RevOps lead or PMO |
| Salesforce admin | The org: packages, permissions, integrations, data loads. | Integration re-pointing; permission changes on cutover. | In-house admin or partner |
| Sales-ops owner | Catalog, pricing rules, templates, approvals. | Target catalog structure; rule re-expression; template sign-off. | Sales operations manager |
| Rep council | Real quotes during the parallel run; adoption. | Whether the new tool is usable on real deals. | 2–3 reps across segments |
Hours per week, by phase
| Phase | Sponsor | Project lead | Admin | Sales ops | Reps (each) |
|---|---|---|---|---|---|
| 1. Discovery (wk 1) | 2 | 10 | 8 | 6 | 1 |
| 2. Catalog & pricing (wk 2–3) | 1 | 6 | 10 | 10 | 0 |
| 3. Install base (wk 4–5) | 1 | 6 | 12 | 4 | 0 |
| 4. Integrations & documents (wk 5–6) | 1 | 6 | 12 | 8 | 2 |
| 5. Parallel run & cutover (wk 7–8) | 2 | 8 | 20 | 10 | 4 |
Indicative hours per week for a 4–8 week Kugamon migration in a 50-user org. Roughly 120–200 internal hours in total; scale up for Revenue Cloud Advanced, where a full rebuild runs 12–18 months in practice.
Who is in the room
Who leads each phase, per Kugamon’s data sheet
Kugamon’s published implementation data sheet splits the engagement into five phases and says who leads each. Your team, or someone you designate, project-manages the whole thing.
| Phase | Lead | Length | What happens |
|---|---|---|---|
| Start | Kugamon | — | Kick-off and install. |
| Setup & training | Kugamon | 4–8 weeks, by functions purchased | Baseline settings, products, accounts; Quote to Cash training; Subscription Management training; a quiz after each block. |
| Build-out | Your admin or a partner | 0–6 weeks, by build items | Plan, design, build, test, deploy. Zero weeks when out-of-box functionality is sufficient. |
| Migrate | Optional | 2–6 weeks, by data condition and size | Access, data load, test. |
| Launch | Kugamon | — | Go-live and check-in. |
Attendance widens as training moves through the process: the project team, org admin and consultants sit in every session; the sales-ops lead, finance liaison and fulfillment rep join for Quote to Cash; the customer-success liaison joins for Subscription Management. That is the practical answer to “who needs to be in the room” for a Kugamon move; the five-role model above is the decision structure around it.
When you need a partner
- Revenue Cloud Advanced. A 12–18 month rebuild in practice — catalog redesign, pricing procedures, integrations, parallel run — is more than most in-house teams can staff alongside their day jobs. Budget for outside help.
- Conga with TurboPricing or heavy Apex. Extracting pricing logic from an off-platform engine or custom code is specialist work.
- No in-house admin. The admin role is 8–20 hours a week for the project; if nobody can give that, a partner fills it.
- Kugamon. Implementation is included in the published fee; a partner is optional and most customers do not use one.
A project lead from RevOps or a PMO who owns the inventory, plan and difference log, backed by an executive sponsor who owns the date and scope. The Salesforce admin owns the org but should not also be the project lead.
Roughly 120–200 hours across five roles for a 4–8 week Kugamon migration in a 50-user org. Revenue Cloud Advanced rebuilds run 12–18 months in practice and scale accordingly.
For Revenue Cloud Advanced, a 12–18 month rebuild in practice usually needs outside help alongside the partner migration tools. For Kugamon, implementation is included in the published fee (AppExchange) and a partner is optional.
How long would yours take?
Readiness check
Twelve questions about your catalog, pricing logic, approvals and integrations. Returns a timeline range.
Take the check →Object mapper
Where every Salesforce CPQ, Conga, Revenue Cloud Advanced, DealHub and Nue object lands — and what has no equivalent.
Look up an object →3-year cost
Published prices where they exist, labelled estimates where they do not, at your user count.
Open the calculator →Nothing is submitted and no email is asked for — all three run in your browser. 134 public AppExchange reviews are on the reviews page.
See your migration plan
Published timelines by source platform, a fixed implementation fee, and a calculator that labels every estimate.