Skip to content

ApisCP Migration Project

Executive Summary

Objective: Migrate from cPanel to ApisCP to eliminate £324 annual licensing costs while maintaining service quality.

Benefits: - Cost Savings: £324/year (£27/month) - Modern Architecture: API-first design with PowerDNS integration - Open Source: No vendor lock-in - Feature Parity: Comparable functionality to cPanel - Enhanced Security: Built-in security features - PowerDNS Integration: Native PowerDNS support for enhanced DNS management

Timeline: Q2-Q3 2025 (estimated 12-16 weeks)

Risk Level: Medium - requires careful planning and phased rollout

Project Status: Preparation phase - licenses purchased (1 Pro, 1 Mini)

Current State

Existing cPanel Infrastructure

Operating System: AlmaLinux 8 (current production servers)

Server License Type Monthly Cost Annual Cost
eu1.cp (CPX31) cPanel Pro £13 £156
ns1 (CX22) cPanel DNS Only £7 £84
ns2 (CX22) cPanel DNS Only £7 £84
Total £27 £324

ApisCP Licenses Acquired

Status: Licenses purchased and ready for deployment

License Type Purpose Status
ApisCP Pro Production hosting server Purchased ✅
ApisCP Mini Test/development server Purchased ✅

License Details: - Pro license for main production hosting operations - Mini license for testing and internal sites - Both licenses support PowerDNS integration

Features in Use

  • ✅ Web hosting (Apache/nginx)
  • ✅ Email services (Exim/Dovecot)
  • ✅ DNS management
  • ✅ MySQL/MariaDB databases
  • ✅ PHP multi-version support
  • ✅ SSL/TLS with Let's Encrypt
  • ✅ File management
  • ✅ Backup management
  • ✅ Account management
  • ✅ Resource monitoring

Target State

ApisCP Feature Comparison

Feature cPanel ApisCP Status
Web Hosting ✅ ✅ Equivalent
Email Services ✅ ✅ Equivalent
DNS Management ✅ ✅ Enhanced with PowerDNS
Database Management ✅ ✅ Equivalent
PHP Support ✅ ✅ Multi-version
SSL/TLS ✅ ✅ Let's Encrypt
Backups ✅ ✅ Equivalent
File Manager ✅ ✅ Modern UI
Email Filtering ✅ ✅ SpamAssassin + Rspamd
API Access Limited ✅ Enhanced
Cost £324/year £0/year Major advantage

ApisCP Advantages

  1. Cost: Completely free, open source
  2. API-First: Modern REST API for automation
  3. Security: Enhanced security features built-in
  4. Performance: Optimised for modern workloads
  5. Flexibility: Highly customisable
  6. Community: Active development community

Potential Challenges

  1. Learning Curve: Different interface from cPanel
  2. Migration Complexity: 30 accounts to migrate
  3. Client Training: Some clients use cPanel directly
  4. DNS Integration: Requires PowerDNS setup
  5. Documentation: Less extensive than cPanel

Migration Strategy

Infrastructure Approach

New Server Deployment Strategy:

Rather than upgrading existing AlmaLinux 8 servers in place, the migration will use a fresh server approach:

  1. New Servers: Provision fresh servers with AlmaLinux 10
  2. Clean Installation: Install ApisCP with PowerDNS on new infrastructure
  3. Account Migration: Migrate client accounts from old cPanel servers to new ApisCP servers
  4. Parallel Operation: Run both environments during transition
  5. Gradual Cutover: Migrate accounts in controlled batches
  6. Decommission: Remove old cPanel servers once migration complete

Benefits of Fresh Server Approach: - ✅ Clean slate - no legacy configuration issues - ✅ Latest OS version (AlmaLinux 10) - ✅ Rollback capability (old servers remain operational) - ✅ No upgrade risks or conflicts - ✅ Testing on production-equivalent hardware

PowerDNS Integration: - ApisCP will be configured with native PowerDNS support - DNS management integrated into ApisCP control panel - Enhanced DNS capabilities (DNSSEC, API-driven zones) - Replaces cPanel DNS with modern DNS infrastructure

Phased Approach

gantt
    title ApisCP Migration Timeline
    dateFormat  YYYY-MM-DD
    section Phase 1: Preparation
    Research & Planning           :2025-04-01, 2w
    Test Environment Setup        :2025-04-15, 1w
    section Phase 2: Testing
    Internal Sites Migration      :2025-04-22, 2w
    Testing & Validation          :2025-05-06, 1w
    section Phase 3: DNS Migration
    PowerDNS Setup                :2025-05-13, 1w
    DNS Migration                 :2025-05-20, 1w
    section Phase 4: Client Migration
    Batch 1 (10 accounts)         :2025-05-27, 2w
    Batch 2 (10 accounts)         :2025-06-10, 2w
    Batch 3 (10 accounts)         :2025-06-24, 2w
    section Phase 5: Completion
    Final Testing                 :2025-07-08, 1w
    cPanel Decommission           :2025-07-15, 1w

Phase 1: Preparation (2 weeks)

Week 1-2: Research & Planning

  • Review ApisCP documentation thoroughly
  • Document all current cPanel configurations
  • Identify potential migration blockers
  • Create detailed migration checklist
  • Set up test environment specifications
  • Plan rollback procedures

Deliverables: - Complete feature comparison matrix - Migration runbook document - Rollback procedure document

Phase 2: Test Environment (3 weeks)

Week 3: Test Server Setup

  • Provision new test server with AlmaLinux 10
  • Install ApisCP with Mini license
  • Configure PowerDNS integration
  • Configure basic settings (email, web, SSL)
  • Set up Let's Encrypt SSL automation
  • Configure email services (Exim + Dovecot)

Week 4-5: Internal Site Testing

Test Phase Sites (Using ApisCP Mini License):

  1. MDHosting.co.uk - Company main website
  2. Full production testing
  3. Contact forms and email functionality
  4. SSL certificate validation

  5. Performance benchmarking

  6. Personnel Sites - Hosting staff personal sites

  7. Various WordPress configurations
  8. Different PHP versions
  9. Email account testing
  10. Real-world usage patterns

Testing Activities: - [ ] Migrate MDHosting.co.uk to ApisCP test server - [ ] Migrate hosting personnel sites to ApisCP test server - [ ] Test all functionality comprehensively - [ ] Document any issues encountered - [ ] Refine migration procedures based on findings - [ ] Create client migration guide and documentation - [ ] Validate PowerDNS DNS management features - [ ] Test API functionality for automation

Success Criteria: - All test sites fully functional on ApisCP - Email sending and receiving working correctly - SSL certificates auto-renewing via Let's Encrypt - Performance equivalent or better than cPanel - PowerDNS DNS management operational - No critical issues identified - Personnel sites operating without intervention - MDHosting.co.uk successfully serving production traffic

Phase 3: DNS Infrastructure (2 weeks)

Week 6: PowerDNS Production Setup

PowerDNS is integrated directly with ApisCP, so DNS migration happens alongside hosting migration.

  • Install PowerDNS on production DNS servers (ns1, ns2)
  • Configure PowerDNS integration with ApisCP
  • Set up zone synchronization from ApisCP to DNS servers
  • Import existing DNS zones from cPanel
  • Configure zone transfer security (TSIG keys)
  • Test zone transfers and updates
  • Configure DNSSEC (optional, future enhancement)
  • Set up API access for ApisCP DNS management

Week 7: DNS Migration and Validation

  • Run parallel DNS (cPanel + PowerDNS) for validation
  • Verify zone data accuracy across all domains
  • Test DNS updates from ApisCP interface
  • Monitor DNS query resolution for both systems
  • Gradually shift traffic to PowerDNS
  • Monitor for 48-72 hours for any issues
  • Decommission cPanel DNS once stable

Success Criteria: - All zones transferred correctly to PowerDNS - DNS queries resolving properly from ns1 and ns2 - TTL values preserved during migration - ApisCP DNS management working correctly - Zone updates propagating from ApisCP to PowerDNS - No DNS-related incidents or resolution failures - DNSSEC ready for future implementation

Phase 4: Client Migration (6 weeks)

Pre-Migration Checklist (Per Account):

  • Full cPanel backup created
  • Database dump verified
  • Email accounts documented
  • DNS records documented
  • SSL certificates noted
  • Cron jobs documented
  • FTP accounts listed
  • Client notification sent

Migration Process (Per Account):

  1. Preparation (Day 1)
  2. Create account in ApisCP
  3. Configure basic settings
  4. Set up email accounts

  5. Configure DNS records

  6. Content Migration (Day 1-2)

  7. Transfer website files
  8. Import databases
  9. Restore email (if needed)
  10. Configure SSL certificates

  11. Set up cron jobs

  12. Testing (Day 2)

  13. Test website functionality
  14. Verify email sending/receiving
  15. Check database connections
  16. Test SSL certificates

  17. Verify DNS resolution

  18. Cut-over (Day 3)

  19. Update DNS to point to new server
  20. Monitor for 24 hours
  21. Address any issues
  22. Client confirmation

Batch Strategy:

Batch 1 (Weeks 8-9): 10 Low-Risk Accounts - Simple WordPress sites - Low traffic - Standard configurations - Used to refine process

Batch 2 (Weeks 10-11): 10 Medium Accounts - More complex sites - Higher traffic - E-commerce platforms - Test scaling procedures

Batch 3 (Weeks 12-13): 10 Remaining Accounts - Any complex or custom setups - High-value clients - Final refinements

Phase 5: Completion (2 weeks)

Week 14: Final Testing

  • Verify all accounts migrated successfully
  • Confirm all services operational
  • Check backup systems
  • Review monitoring alerts
  • Client satisfaction check
  • Document lessons learned

Week 15: cPanel Decommission

  • Final backup of all cPanel data
  • Cancel cPanel licenses
  • Archive cPanel configurations
  • Update all documentation
  • Celebrate £480 annual savings! 🎉

Risk Management

Identified Risks

Risk Probability Impact Mitigation
Data loss during migration Low Critical Full backups before each migration
Email service disruption Medium High Parallel email during transition
Client dissatisfaction Medium Medium Clear communication, training
DNS propagation delays Medium Low Low TTL values pre-migration
Performance degradation Low High Load testing before migration
Extended downtime Low High Strict time limits per migration
Feature gaps discovered Medium Medium Thorough testing in Phase 2

Rollback Procedures

If Critical Issues Arise:

  1. Immediate Actions
  2. Stop all migrations immediately
  3. Assess the situation

  4. Communicate with affected clients

  5. Rollback Process

  6. Revert DNS to original cPanel server
  7. Restore from pre-migration backups
  8. Verify service restoration

  9. Document what went wrong

  10. Recovery Planning

  11. Identify root cause
  12. Develop fix or workaround
  13. Re-test in test environment
  14. Resume migrations when safe

Point of No Return: - cPanel licenses cancelled (Week 15) - Before this point, rollback is always possible

Client Communication

Pre-Migration Communication

2 Weeks Before Migration:

Subject: Important: MDHosting Infrastructure Upgrade

Dear [Client Name],

We're upgrading our hosting infrastructure to provide you with enhanced performance and security. Your account is scheduled for migration on [date].

What to Expect: - Brief maintenance window: [date/time] - Improved performance and security - No action required from you - No changes to your website or emails

Your websites and emails will remain fully functional during this upgrade.

If you have any questions, please don't hesitate to contact us.

Best regards,
MDHosting Ltd

1 Day Before Migration:

Subject: Reminder: Tomorrow's Infrastructure Upgrade

[Brief reminder of maintenance window]

Post-Migration Communication

Migration Complete:

Subject: Infrastructure Upgrade Complete

Dear [Client Name],

Your account has been successfully migrated to our upgraded infrastructure. Everything is now running on our new, enhanced platform.

What's Changed: - Improved security features - Enhanced performance - Modern management interface

What's the Same: - Your website(s): [URLs] - Your email addresses - All your content and data

If you experience any issues, please contact us immediately.

Thank you for your patience during this upgrade.

Best regards,
MDHosting Ltd

Training & Documentation

Internal Documentation Needed

  • ApisCP administration guide
  • Common tasks quick reference
  • Troubleshooting guide
  • Backup and restore procedures
  • Client support procedures

Client-Facing Documentation

  • New control panel access guide
  • Feature comparison (cPanel vs ApisCP)
  • Video tutorials for common tasks
  • FAQ document
  • Support contact information

Success Metrics

Technical Metrics

  • Migration completion rate: 100% target
  • Post-migration incidents: <5% of accounts
  • Average downtime per account: <1 hour
  • Service restoration time: <4 hours if issues
  • Client-reported issues: <10% of accounts

Business Metrics

  • Cost savings: £480/year achieved
  • Client satisfaction: >90% satisfied
  • Support tickets: <20% increase month 1
  • Churn rate: <2% attributable to migration
  • New feature utilisation: Track adoption

Performance Metrics

  • Page load times: Equivalent or better
  • Email delivery: Equivalent or better
  • Server resource usage: Optimised
  • Uptime: Maintain 99.98%

Budget & Resources

Financial Investment

Item Cost Notes
Test Server (if new) £16/month x 3 months May use existing
Additional Backup Storage £10/month x 3 months Temporary
Time Investment ~80 hours 2 hours per account avg
Total Investment ~£100 One-time
Annual Savings £480 Ongoing
ROI 480% First year

Time Allocation

  • Phase 1 (Prep): 16 hours
  • Phase 2 (Testing): 24 hours
  • Phase 3 (DNS): 16 hours
  • Phase 4 (Migration): 60 hours (2h per account)
  • Phase 5 (Completion): 8 hours
  • Total: ~124 hours over 16 weeks

Next Steps

Immediate Actions (This Week)

  1. Review this migration plan thoroughly
  2. Identify any potential issues or concerns
  3. Set up ApisCP test environment
  4. Begin familiarisation with ApisCP interface
  5. Create detailed task checklist

Before Starting Phase 1

  • Confirm all current cPanel configurations documented
  • Verify backup systems fully operational
  • Ensure test environment available
  • Block time in calendar for migration work
  • Set up project tracking system

Appendices

A. ApisCP Resources

  • Official Documentation: https://docs.apiscp.com
  • GitHub Repository: https://github.com/apisnetworks/apnscp
  • Community Forum: https://discord.gg/wDBTz6V
  • Migration Guides: (to be compiled during Phase 1)

B. Automation Scripts

Scripts to be developed during migration:

  • Account backup script
  • Account migration script
  • DNS verification script
  • Post-migration testing script
  • Rollback automation script

C. Vendor Contacts

  • Hetzner Support: (account details in secure store)
  • ApisCP Community: Discord channel

This is a living document and will be updated as the project progresses.

Document Status: Draft
Last Updated: January 2025
Next Review: Before Phase 1 commencement