Microsoft 365 migration and secure setup

Who it is for and when

A Microsoft 365 migration is rarely only about moving email or files. At the same time the organisation needs the right structure for identities, permissions, sharing, devices, security, licences and ongoing management.

Kristensson i Skåne AB helps organisations plan and carry out migration to or between Microsoft 365 environments while establishing a secure and maintainable target environment.

Microsoft’s own current migration guidance treats planning, assessing and remediating the source environment, preparing the target environment, the migration itself and onboarding the users as separate parts of the work.

Examples of situations:

• migration from on-premises Exchange to Exchange Online,
• file servers to be moved to SharePoint and OneDrive,
• the organisation is leaving Google Workspace or another platform,
• two Microsoft 365 tenants are to be merged,
• separation after a divestment or an organisational change,
• Microsoft 365 was introduced gradually and needs re-establishing in a structured way,
• identity and security need modernising at the same time as the migration.

Microsoft today supports migration paths for tenant-to-tenant moves, file servers and various external platforms among others. A migration can cover different Microsoft 365 workloads depending on the scenario.

What we do

1. Assessment. We map the source environment, the data, the identities and the dependencies.
2. Design and preparation. The target environment, the security and the migration model are established.
3. Pilot and migration. We verify the approach before wider delivery.
4. Handover. The environment is documented and passes to ordinary management.

What is included

Current state and scope

We map the source environment and decide together what is actually to be migrated. That can cover:

• users and identities,
• email and calendars,
• SharePoint,
• OneDrive,
• Teams,
• file servers,
• domains,
• groups and permissions,
• clients,
• integrations.

At the same time we identify data or technical debt that perhaps should not come along. A migration is a good moment to tidy up.

Target design

We produce a clear target design for the Microsoft 365 environment. That can cover, for example:

• tenant structure,
• domains,
• Entra ID,
• groups and roles,
• Exchange Online,
• Teams,
• SharePoint,
• OneDrive,
• Intune,
• security settings,
• the sharing model,
• licence requirements.

If you already have a well-functioning target environment the work is adapted accordingly.

Identity and secure setup

Security should not be added after the migration. Where the right licences and prerequisites exist, the work can cover, for example:

• multifactor authentication,
• Conditional Access,
• administrative roles,
• separation of privileged accounts,
• Entra ID,
• Intune and device requirements,
• a basic security baseline,
• external sharing,
• logging.

Microsoft describes Conditional Access as a central Entra capability for bringing signals together and applying access policies; together with Intune, device compliance can also affect access.

Exactly which capabilities are introduced depends on your licences and the agreed scope.

Preparation and pilot

Before a broad migration we check the target environment and run a pilot where needed. The pilot is used to verify:

• identities,
• permissions,
• the data move,
• the user experience,
• client configuration,
• technical dependencies.

Microsoft also recommends pilot groups ahead of broad rollout of SharePoint and OneDrive.

Migration and cutover

The migration is planned in suitable batches or as an agreed cutover. We handle the parts covered by the engagement and follow up the migration result.

For larger or more complex environments the migration can be split by user group, office, workload, company or country.

Verification

After the migration we check that what was to be moved has moved and that the central functions work as intended. Any deviations are documented and handled.

Users and support

A technically correct migration can still go badly for the business if nobody knows what has changed. Where needed we therefore help with:

• a communication plan,
• user information,
• short guides,
• support preparation,
• hypercare after cutover.

Microsoft explicitly raises user onboarding and change management as part of migration planning.

Scope and price

Microsoft 365 migrations vary a great deal in complexity. The proposal therefore always states exactly which workloads and activities are included. Licence costs, third-party tools and larger changes outside the agreed target environment are not automatically included.

The price is driven by the scope above. You get an estimated cost proposal and, where possible, a fixed price.

What do you need to contribute?

We normally need access to the relevant technical environments and to people who know what the business needs.

You also need to take decisions on, for example:

• which information is to be migrated,
• licences,
• structure,
• user groups,
• the timing of the cutover,
• any business constraints.

How it works

1. A first conversation. We listen to your situation and explain how we usually set up the work. You get our assessment straight away, free of charge.
2. A proposal with scope and price. A short written proposal with what is included, what you get, who does the work and what it costs.
3. Delivery and handover. We work together with your organisation, report continuously and hand over so that you can maintain the result yourselves.