https://kilocode-docs.vercel.app/docs/_next/static/chunks/pages/co…/enterprise/migration-dcc31a59f8c6f398.js

1(self.webpackChunk_N_E=self.webpackChunk_N_E||[]).push([[3147],{39881:(e,n,t)=>{(window.__NEXT_P=window.__NEXT_P||[]).push(["/collaborate/enterprise/migration",function(){return t(68740)}])},47650:(e,n,t)=>{"use strict";t.r(n),t.d(n,{fence:()=>a,heading:()=>s,table:()=>d,tbody:()=>u,td:()=>p,th:()=>g,thead:()=>c,tr:()=>m});var i=t(92130),o=t(58838);let a={render:o.NG,attributes:i.a9.fence.attributes};function r(e){return"string"==typeof e?e:i.vw.isTag(e)?e.children.map(r).join(" "):""}let s={render:o.DZ,children:["inline"],attributes:{id:{type:String},level:{type:Number,required:!0,default:1},className:{type:String}},transform(e,n){let t=e.transformAttributes(n),o=e.transformChildren(n),a=t.id&&"string"==typeof t.id?t.id:o.map(r).join(" ").replace(/[?/]/g,"").replace(/\s+/g,"-").toLowerCase();return new i.vw(this.render,{...t,id:a},o)}};var l=t(52914);let d={...i.a9.table,render:l.XI},c={...i.a9.thead,render:l.D1},u={...i.a9.tbody,render:l.vc},m={...i.a9.tr,render:l.Tr},g={...i.a9.th,render:l.Th,attributes:{...i.a9.th.attributes,width:{type:String}}},p={...i.a9.td,render:l.Td,attributes:{...i.a9.td.attributes,colspan:{type:Number},rowspan:{type:Number}}}},68740:(e,n,t)=>{"use strict";t.r(n),t.d(n,{__N_SSG:()=>h,default:()=>y,markdoc:()=>f});var i=t(11872),o=t(34904),a=t(92130),r=t(55442),s=t(71867),l=t(47650),d=t(69450);let c={tags:(0,r.X)(s),nodes:(0,r.X)(l),functions:(0,r.X)(d),...(0,r.X)({})},u=new a.Ay.Tokenizer({allowComments:!0}).tokenize("---\ntitle: \"Migration\"\ndescription: \"Migrate your team to Kilo Code Enterprise\"\n---\n\n# Migration\n\nSwitch to **Kilo Teams** or **Kilo Enterprise** from other AI coding tools and experience transparent pricing, no vendor lock-in, and superior team management capabilities.\n\n## Why Teams Switch to Kilo\n\n### Transparency vs. Opacity\n\n**Other AI coding vendors** hide their true costs behind opaque subscription models, leaving you wondering what you're actually paying for.\n\n**Kilo Teams** and **Kilo Enterprise** show you what each AI request costs. Model inference is charged at provider rates with no markup, and credit purchases have a disclosed 5% payment-processing fee.\n\n### No Rate Limiting\n\n**Other tools** slow you down with rate limits and model switching when you need AI most.\n\n**Kilo Teams** and **Kilo Enterprise** never limit your usage - pay for what you use, use what you need.\n\n### True Team Management\n\n**Other solutions** offer basic user management with limited visibility.\n\n**Kilo Teams** provides comprehensive team analytics, role-based permissions, and detailed usage insights, while **Kilo Enterprise** adds advanced governance, audit logging, and enterprise-level security controls.\n\n## Migrating from Cursor\n\n### What You're Leaving Behind\n\n- **Opaque pricing** - Never knowing true AI costs\n- **Rate limiting** during peak usage periods\n- **Limited team visibility** into usage patterns\n- **Vendor lock-in** with proprietary systems\n- **Hidden model switching** that degrades quality\n\n### What You Gain with Kilo Teams or Kilo Enterprise\n\n- **Transparent AI costs** - See exactly what providers charge\n- **No rate limiting** - Use AI when you need it most\n- **Comprehensive analytics** - Understand team usage patterns\n- **Open source extension** - No vendor lock-in\n- **Consistent quality** - No hidden model downgrades\n- **Enterprise controls** _(Enterprise only)_ - SSO, audit logs, and advanced configuration options\n\n### Migration Process\n\n**Step 1: Team Assessment**\n\n1. **Audit current Cursor usage** across your team\n2. **Identify active users** and their usage patterns\n3. **Calculate current costs** (if visible) vs. Kilo pricing\n4. **Plan migration timeline** to minimize disruption\n\n**Step 2: Kilo Setup**\n\n1. **Create organization** at [app.kilo.ai](https://app.kilo.ai)\n2. **Subscribe to Teams ($15/user/month)** or **Enterprise ([Contact Sales](https://kilo.ai/contact-sales))**\n3. **Configure team settings** and usage policies\n4. **Purchase initial AI credits** based on usage estimates\n\n**Step 3: Team Migration**\n\n1. **Invite team members** to Kilo\n2. **Install Kilo Code extension** alongside Cursor initially\n3. **Migrate projects gradually** starting with non-critical work\n4. **Train team** on Kilo Code features and workflows\n\n**Step 4: Full Transition**\n\n1. **Monitor usage patterns** in Kilo dashboard\n2. **Optimize settings** based on team feedback\n3. **Cancel Cursor subscriptions** once fully migrated\n4. **Uninstall Cursor** from team machines\n\n### Cursor Feature Mapping\n\n| Cursor Feature | Kilo Equivalent |\n|---|---|\n| AI Chat | Chat interface with multiple modes |\n| Code Generation | Code mode with advanced tools |\n| Code Editing | Fast edits and surgical modifications |\n| Codebase Understanding | Codebase indexing and search |\n| Team Management | Comprehensive team dashboard (Enterprise adds SSO, audit logs) |\n| Usage Analytics | Detailed usage and cost analytics |\n\n## Migrating from GitHub Copilot\n\n### Limitations You're Escaping\n\n- **Limited model choice** - Stuck with GitHub's model selection\n- **Basic team features** - Minimal team management capabilities\n- **No cost visibility** - Hidden usage costs in subscription\n- **Microsoft ecosystem lock-in** - Tied to Microsoft services\n- **Limited customization** - Few options for team-specific needs\n\n### Kilo Advantages\n\n- **Multiple AI providers** - Choose from 18+ model providers\n- **Advanced team management** - Roles, permissions, and analytics\n- **Transparent pricing** - See exact costs for every request\n- **Provider flexibility** - Switch providers or use your own API keys\n- **Extensive customization** - Custom modes and team policies\n- **Enterprise-level governance** _(Enterprise only)_ - Model filtering, audit logging, and compliance support\n\n### Migration Strategy\n\n**Phase 1: Parallel Usage (Week 1-2)**\n\n1. **Keep GitHub Copilot** active during transition\n2. **Install Kilo Code** extension for team members\n3. **Start with simple tasks** in Kilo Code\n4. **Compare results** and team satisfaction\n\n**Phase 2: Gradual Transition (Week 3-4)**\n\n1. **Use Kilo Code** for new projects\n2. **Migrate existing projects** one at a time\n3. **Train team** on advanced features\n4. **Optimize usage patterns** based on analytics\n\n**Phase 3: Full Migration (Week 5+)**\n\n1. **Disable GitHub Copilot** for most team members\n2. **Cancel GitHub Copilot** subscriptions\n3. **Optimize Kilo Plan** settings\n4. **Document new w

1orkflows** and best practices\n\n### GitHub Copilot Feature Comparison\n\n| GitHub Copilot | Kilo | Advantage |\n|---|---|---|\n| Code suggestions | AI-powered code generation | ✅ More model choices |\n| Chat interface | Multi-mode chat system | ✅ Specialized modes |\n| Team admin | Comprehensive team management | ✅ Enterprise adds audit logs |\n| Usage insights | Detailed usage and cost tracking | ✅ Transparent pricing |\n| Model selection | 18+ AI providers and models | ✅ No vendor lock-in |\n\n## Migrating from Other AI Coding Tools\n\n### Common Migration Patterns\n\n**From Tabnine**\n\n- **Benefit:** More advanced AI models and team features\n- **Process:** Export settings, migrate team, configure advanced features\n- **Timeline:** 1-2 weeks for full transition\n\n**From CodeWhisperer**\n\n- **Benefit:** Escape AWS ecosystem lock-in, better team management\n- **Process:** Parallel usage, gradual migration, team training\n- **Timeline:** 2-3 weeks for enterprise teams\n\n**From Replit AI**\n\n- **Benefit:** Use in VS Code instead of web-based IDE\n- **Process:** Export projects, set up local development, team onboarding\n- **Timeline:** 3-4 weeks including development environment setup\n\n### Universal Migration Checklist\n\n**Pre-Migration Planning**\n\n- [ ] Audit current AI coding tool usage\n- [ ] Identify team members and their roles\n- [ ] Calculate current costs vs. Kilo pricing\n- [ ] Plan migration timeline and milestones\n- [ ] Prepare team communication and training\n\n**Migration Execution**\n\n- [ ] Set up Kilo Organization\n- [ ] Configure team settings and policies\n- [ ] Invite team members and assign roles\n- [ ] Install Kilo Code extension across team\n- [ ] Start with pilot projects or non-critical work\n\n**Post-Migration Optimization**\n\n- [ ] Monitor usage patterns and costs\n- [ ] Optimize team settings based on analytics\n- [ ] Train team on advanced features\n- [ ] Cancel previous AI coding tool subscriptions\n- [ ] Document new workflows and best practices\n\n## Technical Migration: Rules and Configurations\n\nKilo Code uses a compatible rules system that supports Cursor and Windsurf patterns. Migrating your custom rules and configurations is straightforward and typically takes 5-10 minutes per project.\n\n**Quick Overview:**\n\n- **Project rules**: `.cursor/rules/*.mdc` → `.kilo/rules/*.md` (remove YAML frontmatter, keep Markdown content)\n- **Legacy rules**: `.cursorrules` → `.kilo/rules/legacy-rules.md`\n- **AGENTS.md**: Works identically in Kilo Code (no conversion needed)\n- **Global rules**: Recreate in `~/.kilo/rules/*.md` directory\n\nKilo Code also supports mode-specific rules (`.kilo/rules-{mode}/`), which Cursor and Windsurf don't have. This allows different rules for different workflows (e.g., Code mode vs Debug mode).\n\n**\uD83D\uDC49 For detailed step-by-step instructions, format conversion examples, troubleshooting, and advanced migration scenarios, see our [Technical Migration Guide](/docs/getting-started/migrating).**\n\n## Cost Comparison Analysis\n\n### Hidden Costs in Other Tools\n\n**Subscription Models Hide True Costs**\n\n- Monthly fees regardless of actual usage\n- No visibility into per-request costs\n- Rate limiting forces inefficient workflows\n- Model switching without notification\n\n**Kilo Transparent Pricing**\n\n- Pay exactly what AI providers charge\n- See cost of every request in real-time\n- No rate limiting or usage restrictions\n- Choose optimal models for each task\n\n### ROI Calculation Framework\n\n**Current Tool Analysis**\n\n1. **Monthly subscription costs** \xd7 team size\n2. **Hidden productivity losses** from rate limiting\n3. **Opportunity costs** from limited model access\n4. **Management overhead** from poor team visibility\n\n**Kilo Benefits**\n\n1. **Transparent AI costs** (typically 30-50% lower)\n2. **Productivity gains** from no rate limiting\n3. **Better outcomes** from optimal model selection\n4. **Reduced management time** with comprehensive analytics\n\n## Team Training and Adoption\n\n### Training Program Structure\n\n**Week 1: Basics**\n\n- Kilo Code extension installation and setup\n- Basic chat interface and mode usage\n- Understanding transparent pricing model\n- Team dashboard overview\n\n**Week 2: Advanced Features**\n\n- Custom modes and specialized workflows\n- Advanced tools and automation\n- Team collaboration features\n- Usage optimization strategies\n\n**Week 3: Team Optimization**\n\n- Analytics review and insights\n- Cost optimization techniques\n- Workflow integration and best practices\n- Advanced team management features\n\n### Adoption Best Practices\n\n**Start Small**\n\n- Begin with volunteer early adopters\n- Use for non-critical projects initially\n- Gather feedback and iterate\n- Expand gradually across team\n\n**Provide Support**\n\n- Dedicated migration support channel\n- Regular check-ins with team members\n- Documentation and training resources\n- Quick resolution of issues and questions\n\n**Measure Success**\n\n- Track usage adoption rates\n- Monitor cost savings and efficie

1ncy gains\n- Collect team satisfaction feedback\n- Document success stories and best practices\n\n## Common Migration Challenges\n\n### Technical Challenges\n\n**Extension Conflicts**\n\n- **Issue:** Multiple AI coding extensions interfering\n- **Solution:** Disable old extensions during transition\n- **Prevention:** Staged migration with clear timelines\n\n**Workflow Disruption**\n\n- **Issue:** Team productivity dip during transition\n- **Solution:** Parallel usage period with gradual migration\n- **Prevention:** Comprehensive training and support\n\n**Settings Migration**\n\n- **Issue:** Lost customizations from previous tools\n- **Solution:** Document and recreate important settings\n- **Prevention:** Settings audit before migration\n\n**Rules and Configuration Migration**\n\n- **Issue:** Custom rules and configurations not migrating automatically\n- **Solution:** Follow the [technical migration guide](/docs/getting-started/migrating) to manually migrate rules\n- **Prevention:** Audit rules before migration, use version control for rules\n\n### Organizational Challenges\n\n**Change Resistance**\n\n- **Issue:** Team members reluctant to switch tools\n- **Solution:** Demonstrate clear benefits and provide training\n- **Prevention:** Involve team in migration planning\n\n**Budget Approval**\n\n- **Issue:** Finance team concerns about new tool costs\n- **Solution:** Provide detailed cost comparison and ROI analysis\n- **Prevention:** Transparent pricing documentation\n\n**Timeline Pressure**\n\n- **Issue:** Pressure to migrate quickly without proper planning\n- **Solution:** Phased migration approach with clear milestones\n- **Prevention:** Realistic timeline planning with buffer time\n\n## Migration Support\n\n### Professional Migration Services\n\n- **Migration planning** and timeline development\n- **Team training** and onboarding support\n- **Custom integration** development\n- **Ongoing optimization** consulting\n\n### Self-Service Resources\n\n- **Migration guides** for specific tools\n- **[Technical migration guide](/docs/getting-started/migrating)** for rules and configurations (Cursor/Windsurf)\n- **Video tutorials** for common migration scenarios\n- **Community support** through Discord and forums\n- **Documentation** and best practices\n\n### Getting Migration Help\n\n- **Email:** [email protected]\n- **Discord:** Join our migration support channel\n- **Consultation:** Schedule free migration planning call\n- **Documentation:**\n  - [Business migration guide](/docs/collaborate/enterprise/migration) (this page)\n  - [Technical migration guide](/docs/getting-started/migrating) (rules and configurations)\n\n## Success Stories\n\n### Mid-Size Software Company (25 developers)\n\n**Previous:** Cursor Pro subscriptions  \n**Challenge:** High costs with limited visibility  \n**Result:** 40% cost reduction with better team insights  \n**Timeline:** 3-week migration with zero productivity loss\n\n### Enterprise Development Team (100+ developers)\n\n**Previous:** GitHub Copilot Enterprise  \n**Challenge:** Limited model choice and team management  \n**Result:** Improved code quality and team collaboration  \n**Timeline:** 6-week phased migration across multiple teams\n\n### Startup Engineering Team (8 developers)\n\n**Previous:** Multiple individual AI tool subscriptions  \n**Challenge:** Expense report chaos and no team coordination  \n**Result:** Centralized billing and improved team efficiency  \n**Timeline:** 1-week migration with immediate benefits\n\n## Next Steps\n\n- [Get started with your team](/docs/collaborate/teams/getting-started)\n- [Explore team management features](/docs/collaborate/teams/team-management)\n- [Understand billing and pricing](/docs/collaborate/teams/billing)\n- [Migrate your rules and configurations](/docs/getting-started/migrating) (technical guide)\n\nReady to make the switch? Contact our migration team at [email protected] to plan your transition to transparent AI coding.\n"),m=a.Ay.parse(u,{slots:!1}),g=m.attributes.frontmatter?o.Ay.load(m.attributes.frontmatter):{},{components:p}=(0,r._)(c);var h=!0;let f={frontmatter:g};function y(e){let n=e.markdoc;return a.ZR.react(n.content,i,{components:{...p,...e.components}})}},69450:(e,n,t)=>{"use strict";t.r(n),t.d(n,{includes:()=>

1i,upper:()=>o});let i={transform(e){let[n,t]=Object.values(e);return!!Array.isArray(n)&&n.includes(t)}},o={transform(e){let n=e[0];return"string"==typeof n?n.toUpperCase():n}}},71867:(e,n,t)=>{"use strict";t.r(n),t.d(n,{browserFrame:()=>f,callout:()=>o,codicon:()=>a,copyLine:()=>r,flowDiagram:()=>h,icon:()=>d,image:()=>c,imageGallery:()=>u,kiloCodeIcon:()=>m,linebreak:()=>y,tab:()=>l,tabs:()=>s,video:()=>g,youtube:()=>p});var i=t(58838);let o={render:i.Pq,children:["paragraph","tag","list"],attributes:{title:{type:String,description:"Optional custom title for the callout"},type:{type:String,default:"note",matches:["generic","note","tip","info","warning","danger"],description:"The type of callout: generic (no icon/title), note, tip, info, warning, or danger"},collapsed:{type:Boolean,default:!1,description:"When true, the callout starts collapsed and can be expanded by clicking the header"}}},a={render:i.W6,selfClosing:!0,attributes:{name:{type:String,required:!0,description:"The name of the VS Code codicon (e.g., 'send', 'check', 'warning')"},size:{type:String,default:"1em",description:"The size of the icon (CSS font-size value)"},className:{type:String,default:"",description:"Additional CSS classes to apply to the icon"}}},r={render:i.a7,selfClosing:!0,attributes:{text:{type:String,required:!0,description:"The exact one-line text to display and copy"}}},s={render:i.tU,children:["tab"],attributes:{}},l={render:i.oz,children:["paragraph","tag","list","fence","heading"],attributes:{label:{type:String,required:!0,description:"The label shown on the tab button"}}},d={render:i.In,selfClosing:!0,attributes:{src:{type:String,required:!0},srcDark:{type:String,description:"Optional image source for dark mode. Falls back to src if not provided."},alt:{type:String,default:"icon"},size:{type:String,default:"1.2em"}}},c={render:i._V,selfClosing:!0,attributes:{src:{type:String,required:!0,description:"The image source URL"},alt:{type:String,required:!0,description:"Alternative text for the image"},width:{type:String,description:"Width of the image (e.g., '500px', '80%')"},height:{type:String,description:"Height of the image (e.g., '300px', 'auto')"},caption:{type:String,description:"Optional caption displayed below the image"}}},u={render:i.i_,children:["tag"],attributes:{columns:{type:String,description:"Preferred number of image columns on wide screens"},width:{type:String,description:"Preferred width of each gallery image"}}},m={render:i.kz,selfClosing:!0,attributes:{size:{type:String,default:"1.2em",description:"Size of the icon (CSS height value)"}}},g={render:i.n5,selfClosing:!0,attributes:{url:{type:String,required:!0,description:"The YouTube video URL"},title:{type:String,description:"Accessible title for the video iframe"},caption:{type:String,description:"Optional caption to display below the video"}}},p={render:i.Yu,selfClosing:!0,attributes:{url:{type:String,required:!0,description:"The YouTube video URL"},title:{type:String,description:"Accessible title for the video iframe"},caption:{type:String,description:"Optional caption to display below the video"}}},h={render:i.Cb,selfClosing:!0,attributes:{name:{type:String,required:!0,description:"Name of the diagram to render (must match a key in diagrams/index.ts)"},height:{type:String,default:"400px",description:"Height of the diagram container"}}},f={render:i.AR,children:["paragraph","tag","list"],attributes:{url:{type:String,description:"Optional URL to display in the address bar"},caption:{type:String,description:"Optional caption below the frame"}}},y={render:"br",selfClosing:!0}}},e=>{e.O(0,[8228,2545,636,6593,8792],()=>e(e.s=39881)),_N_E=e.O()}]);