Separating Sage 200 into two secure, independent Azure environments

The challenge

• The technology was approaching the end of its supported life
• Users relied on a shared connection method, making activity harder to trace
• Financial data, access and administration had to be separated securely
• The transition had to protect business-critical information and avoid unnecessary disruption

How SNO delivered it

• Understand the requirements: SNO reviewed the existing service, the planned company separation and each organisation’s security and access needs
• Build two environments: two modern Azure platforms so data, administration and access are managed separately
• Separate and migrate: the Sage specialist divided the company data, moved it to the correct environment and configured access for each team
• Test and transition: the combined team checked data, permissions and day-to-day use before completing the move

The outcome

• Stronger security: individual sign-ins give better access control and clearer accountability
• Complete separation: each business controls its own data, administration and users
• A simpler user experience: secure access to Sage 200 without the previous VPN process
• Reduced operational risk: modern, supported technology replaces ageing systems and access methods

Why it matters

Business separations, mergers and restructures often leave shared systems that nobody fully owns. Rebuilding them as separate, supported cloud services removes that risk and gives each organisation a clean, auditable starting point.