Migrations and integrations, from assessment to aftercare.
Start with the move or the problem that needs attention. We assess it, agree a fixed-scope project and hand it over to your team. Optional monthly support keeps connected systems healthy. Scope and price are agreed before you commit.
Readiness assessment
Before anything moves, we document what you have, what depends on it and what could go wrong. You leave with a plan, a realistic timeline and a fixed price for the project.
- Inventory. Users, mailboxes, sites, files, permissions, databases and the apps connected to them.
- Dependencies. The integrations, syncs and reports that could break when something moves.
- Risks and options. What could go wrong, how to avoid it and the trade-offs between approaches.
- Plan and price. Pilot, cutover approach, rollback step and a fixed project price. The assessment fee is credited if you go ahead.
Migration or integration project
The move, the fix or the workflow, delivered on a fixed scope with a pilot first and a cutover checklist you sign off.
- Pilot first. A small group or data set moved and checked before the rest.
- Data copied ahead. Most data synced before the switch, so cutover is short.
- Your sign-off. Cutover timed outside your busy hours, with a rollback step.
- Handover pack. What changed, where things live now, access lists and how to get help.
Integration support
Monthly care for the syncs, pipelines and workflows your business depends on. Month to month, cancel any time.
- Monitoring. Checks and failure alerts on the agreed systems, with response hours documented.
- Fixes. Broken syncs and changes in connected tools handled for you.
- Monthly health summary. What ran, what failed, what was fixed and what to watch.
- Small improvements. Including new workflows when the numbers justify them.
What to establish before you start.
Which platforms do you work with?
Microsoft 365, SharePoint, Exchange and Azure in depth, plus Google Workspace, file servers, SQL databases and business apps with an API. Fit is confirmed in the assessment.
What affects the cost of a migration?
The number of users and mailboxes, data volume, how tangled the permissions are, the systems connected to it and how much downtime you can accept. Licences and tool costs are listed separately in the proposal.
Can you fix an integration someone else built?
Often, yes. We start by finding where data travels and where it fails, then agree whether to repair, rebuild or replace it.
What should we bring to the first conversation?
The systems involved, roughly how many users or records, your deadline and what is worrying you. Describe your move.
Not sure where to start?
15 minutes, no slides. If we are not the right fit, we will say so.
Request a 15-minute call