Projects and migrations
Microsoft 365 and Azure projects
Not everything is an ongoing service. These are pieces of work with a beginning and an end — a migration, a deployment, a tenant move — priced and run as projects.
Azure solutions and migrations
-
Microsoft 365 GCC High migration
The move a defense contractor makes when DoD CUI or export-controlled data is on the table. A new tenant in Microsoft's government cloud, scoped before anything is copied.
-
Azure Virtual Desktop
A full Windows desktop delivered from Azure, so staff get the same environment from any device, anywhere, and it stays under your control rather than living on a laptop. Access is built on identity and conditional access rather than a VPN nobody wants to use.
-
On-Premises to Microsoft 365
Email, files and identity moved off your own servers into Microsoft 365, including the part most migrations underestimate — deciding what does not come with you.
-
Google Workspace to Microsoft 365
Mail, drive and identity moved across from Google, with the shared-drive structure mapped properly instead of dumped into someone's OneDrive.
-
Azure Database Migration
Moving databases off ageing on-premises servers into Azure, sized so you are not paying for capacity you never use.
Microsoft licensing
We resell Microsoft 365 GCC High, Azure Government and Microsoft 365 Commercial. GCC and Azure Government Secret are not on the list. If you need a program that isn't listed here, we'll tell you rather than take the order and work it out afterwards.
Licensing has a page of its own — where the money usually leaks, and how GCC High, Azure Government and Commercial fit together.
-
Microsoft 365 GCC High Licensing
GCC High and Azure Government licensing for contractors who hold DoD CUI or ITAR data, plus Commercial Microsoft 365. Eligibility is validated by Microsoft first, and government licensing comes through an authorized government channel.
-
Microsoft 365 Commercial Licensing
Standard Microsoft 365 licensing for businesses with no CUI obligation, including working out which plan you actually need rather than the one with the most features.
Before you commit to a migration
Every one of these depends on the state of what you have now — how much data, how it is structured, what is still running on something unsupported, and how quickly your side can make decisions. Which is why we scope before quoting rather than after.
If CUI is anywhere in scope, that changes the order of operations. The boundary gets designed first and the migration follows it, not the other way round. Moving the data and working out the boundary afterwards is how contractors end up doing it twice.
Related: what this costs, the GCC High migration checklist, and who is responsible for what.
Got a project in mind?
Tell us what you're moving and what you're moving it from. Fifteen minutes, no obligation.
Schedule a call