Best Practices for Transitioning from One ERP Hosting Provider to Another

A Guide for Microsoft Dynamics 365 Business Central Customers

Changing ERP hosting providers is one of the most significant technology decisions an organization can make. Whether driven by escalating costs, poor service levels, limited expertise, security concerns, aging infrastructure, or a desire to modernize onto Microsoft Azure, a well-planned transition can improve reliability, performance, security, and user satisfaction.

However, an ERP hosting migration also introduces risk. Poor planning can result in business disruption, data loss, security vulnerabilities, and unexpected costs.

This article outlines best practices, identifies the technical specialists commonly required, and highlights the risks organizations should evaluate before making the move.  Please see the link at the end of this article to request a copy of the Transition Readiness Assessment.  This assessment will let you know how ready you are to transition.

Why Companies Change ERP Hosting Providers

Common reasons include:

• Poor responsiveness from the current hosting provider
• Frequent outages or performance issues
• Escalating monthly costs
• Lack of Business Central expertise
• Limited disaster recovery capabilities
• Inadequate cybersecurity controls
• Need to migrate to Microsoft Azure
• End-of-life infrastructure concerns
• Regulatory or compliance requirements
• Desire for a more strategic IT partner

While these reasons are valid, organizations should approach any migration with caution and a structured methodology.

Best Practices for a Successful ERP Hosting Transition

1. Perform a Comprehensive Discovery Assessment

Before any migration begins, document the existing environment:

Infrastructure Inventory

• Servers and virtual machines
• CPU, RAM, and storage utilization
• SQL Server versions and licensing
• Active Directory dependencies
• VPN configurations
• Third-party integrations
• Reporting tools
• Backup systems
• Security appliances

ERP Inventory

• Business Central version
• Custom modifications
• ISV applications
• Job queues
• Scheduled tasks
• Interfaces and APIs
• Power BI integrations
• EDI connections
• Warehouse devices
• Mobile applications

Organizations are often surprised to discover critical dependencies that were never formally documented.

2. Establish Clear Business Objectives

Determine what success looks like.

Examples include:

• Reduce downtime
• Improve system performance
• Lower operational costs
• Enhance cybersecurity
• Improve support responsiveness
• Upgrade to a supported BC version
• Implement disaster recovery
• Support future growth

Technology decisions should align with business outcomes.

3. Review All Contracts Carefully

Examine existing agreements for:

• Termination clauses
• Notice requirements
• Data ownership provisions
• Administrative access rights
• Source code ownership
• Backup retrieval procedures
• Exit assistance obligations
• Licensing responsibilities

Do not assume your provider will automatically cooperate during transition.

4. Validate Backup and Recovery Procedures

Before migration:

• Obtain complete database backups.
• Verify restore procedures.
• Request copies of ERP application servers.
• Export Business Central configurations.
• Preserve encryption certificates.
• Document recovery objectives.

Conduct a test restoration before production migration.

5. Design the Future-State Environment

Architect the target environment based upon growth projections.

Typical Azure considerations include:

Compute

• Appropriate VM sizing
• Availability Zones
• Reserved Instances

Storage

• Std or Premium SSD storage
• Managed disks
• Backup vaults

Networking

• Site-to-site VPNs
• Azure Virtual Networks
• Network segmentation

Security

• Multifactor authentication
• Conditional Access policies
• Endpoint protection
• Security monitoring

Business Continuity

• Geo-redundant backups
• Disaster recovery replication
• Defined RTO/RPO objectives

6. Conduct Multiple Test Migrations

Never migrate directly into production.

Recommended phases:

Phase 1

Proof-of-concept migration.

Phase 2

User acceptance testing.

Phase 3

Parallel production validation.

Phase 4

Final cutover.

Testing significantly reduces operational risk.

7. Develop a Detailed Cutover Plan

A written cutover schedule should include:

• Freeze dates
• Backup timing
• Data synchronization steps
• DNS changes
• VPN activation
• Validation procedures
• Communication plans
• Rollback procedures
• Responsibilities by team member

Every participant should know exactly what occurs and when.

8. Communicate Frequently With End Users

Users should understand:

• Planned downtime windows
• New login procedures
• Changes in performance expectations
• Training requirements
• Support escalation paths

Poor communication creates unnecessary anxiety.

9. Monitor Closely After Go-Live

The first 30–60 days require heightened support.

Monitor:

• Application performance
• SQL database optimization/performance
• User experience
• Backup success rates
• Security alerts
• Integration processing
• Batch jobs

Many issues only emerge under actual production loads.

Technical Specialists Often Needed

Successful ERP hosting migrations require expertise from multiple disciplines.

Azure Infrastructure Specialists

Azure Solutions Architect

Responsibilities:

• Overall environment design
• Capacity planning
• High availability architecture
• Disaster recovery planning

Azure Systems Engineer

Responsibilities:

• Virtual machine deployment
• Storage configuration
• Monitoring setup
• Resource optimization

Network Engineer

Responsibilities:

• VPN configuration
• Firewall rules
• Routing validation
• Connectivity troubleshooting

Identity and Security Specialist

Responsibilities:

• Active Directory integration
• Entra ID configuration
• Multifactor authentication
• Conditional Access implementation

Cybersecurity Specialist

Responsibilities:

• Vulnerability assessments
• Security hardening
• Threat monitoring
• Compliance validation

Microsoft Business Central Specialists

Business Central Functional Consultant

Responsibilities:

• Business process review
• Configuration validation
• User testing coordination
• Training support

Business Central IT Technical Consultant

Responsibilities:

• Service tier configuration
• Environment setup
• Performance optimization
• Extension deployment

Business Central Developer

Responsibilities:

• Custom extension migration
• Code remediation
• API integration support
• Upgrade modifications

SQL Server Database Administrator

Responsibilities:

• Database migration
• SQL database optimization/Performance fine tuning
• Backup validation
• Maintenance planning

Integration Specialist

Responsibilities:

• EDI testing
• API validation
• Third-party connectivity
• Middleware troubleshooting

Project Manager

Responsibilities:

• Schedule coordination
• Risk management
• Resource allocation
• Executive reporting

A strong project manager often determines the success or failure of the transition.

Major Risks of ERP Hosting Migrations

Organizations should proactively identify and mitigate risks.

Operational Risks

• Extended downtime
• Failed cutovers
• Incomplete testing
• User productivity losses

Technical Risks

• Data corruption
• Data loss
• Integration failures
• Performance degradation
• Incompatible extensions

Security Risks

• Exposed administrative credentials
• Misconfigured firewalls
• Unsecured remote access
• Insufficient logging and monitoring

Financial Risks

• Unexpected consulting expenses
• Licensing gaps
• Azure consumption overruns
• Duplicate hosting costs during transition

Business Risks

• Delayed shipments
• Inability to invoice customers
• Inventory inaccuracies
• Customer dissatisfaction

Vendor Risks

• Limited cooperation from incumbent provider
• Incomplete documentation
• Delayed access to backups
• Disputes regarding ownership rights

Personnel Risks

• Key employee departures
• Lack of internal expertise
• Insufficient training

Questions to Ask a Prospective Hosting Provider

Before selecting a new ERP hosting partner, ask:

1. How many Business Central environments do you actively manage?
2. Are you a Microsoft Business Solutions Partner?
3. What are your response time commitments?
4. What disaster recovery capabilities are included?
5. How are backups managed and tested?
6. What cybersecurity measures are standard?
7. Will we have administrative access?
8. Who owns the environment documentation?
9. Can you provide customer references?
10. What support is available during and after cutover?

The answers often reveal whether the provider is a true strategic partner or merely a hosting vendor.

Final Thoughts

Transitioning to a new ERP hosting provider represents both opportunity and risk. Organizations that invest in planning, testing, communication, and experienced technical leadership dramatically improve their chances of success.

The right hosting partner should deliver more than infrastructure. They should provide strategic guidance, deep Business Central expertise, proactive security, responsive support, and a roadmap for future growth.

ERP systems are mission-critical. A thoughtful transition protects the business while positioning it for long-term success.

When done correctly, changing hosting providers is not simply an IT project—it is an investment in operational resilience, security, and the future of the organization.

 

Get your copy of Hosting Transition Readiness Assessment

First Name *

Last Name *

Email Address *

Phone Number

Message0 / 180

Submit