Microsoft 365, Google Workspace and Atlassian

Which platform do you run on

Three platforms that most companies run on. We take them from deployment through migration to daily administration. We do not push one at any cost: we pick the one that fits how you work and what you already have.

Microsoft 365

Tenant, identity and permissions, mail, Teams and SharePoint, security policies and licences.

  • Entra ID: accounts, groups, sign-in and MFA
  • Exchange: mail, rules, phishing protection
  • SharePoint and Teams: file structure and permissions
  • Licence selection and order in subscriptions

Deployment, migration and ongoing administration

Google Workspace

Domain and account configuration, shared drives, security rules and migrations between platforms.

  • Accounts and organisational units
  • Gmail: domain, rules and mail protection
  • Shared drives: structure and access
  • Meet and working on documents together

Deployment, migration and ongoing administration

Atlassian

Jira, Confluence, Jira Service Management and Assets: deployments, cleaning up inherited instances, migrations to Cloud.

  • Jira: projects, schemes and workflows
  • Confluence: knowledge base and documentation
  • Jira Service Management: portal and queues
  • Assets and CMDB: hardware, licences, dependencies

Audit of an existing instance from 3 working days

One team runs all three platforms, so moving between them or working in a mixed environment does not require two suppliers.

What we do in these systems

Six things clients ask about most often. We take each one from the decision to a working environment.

Deployment from scratch

We set up the tenant or domain, move accounts, configure password and sign-in policy. A new hire has mail, files and chat on day one.

Migration from what you have

A mail server on your premises, another domain, a second platform or Data Center to Cloud. A plan, a cutover window and a check that nothing was left behind.

Identity and access

One account for everything, two-factor sign-in, groups instead of granting rights one by one. When someone leaves, access closes everywhere.

Request portal and self-service

Jira Service Management instead of a shared mailbox: service catalogue, queues and SLA. Every request has a number, an owner and a deadline.

Assets and CMDB

Hardware, licences and dependencies in one model. A request lands on a specific asset, not in an empty description field.

Licences and cost

We check what you pay for and what nobody uses. The plan follows how people actually work, not the price list.

Where we migrate from

Migration is the most common reason companies come to us. Four scenarios we run regularly.

A mail server on your premises

Exchange or another server in your own server room. We move mailboxes, calendars and contacts, and the old server stays read-only during the transition.

From one platform to the other

Microsoft 365 to Google Workspace or the other way round. We map accounts, move mail and files, and keep addresses and aliases intact.

Atlassian Data Center to Cloud

A migration plan, field mapping and removal of what stopped being used years ago. The Cloud instance starts without the inherited mess.

ServiceNow to Jira Service Management

We move the service catalogue, queues and request history, and rebuild the support process where the old one did not work.

Results at clients

Two deployments where what changed was not the tool but the way people work. What we found, what we built and what the client got out of it.

Projects no longer wait for a full mailbox

Industry and size:
Boiler manufacturing, 140 people
Starting point:
The whole company ran projects in Excel files and over email. One person with a full mailbox or a day off was enough to stall the work until someone dug out the right message or updated the spreadsheet. Nobody could see where the project actually stood.
What we did:
We deployed the Atlassian stack: Jira, Confluence and Jira Service Management. Each team got its own project with stages and tasks. The workshops showed the teams depend on each other, so we linked the projects with an integration: you delegate a task from the main project to another team, and closing it updates the parent project on its own.
Timeline:
6 months
Result:
Teams can see who is doing what and where it stands, and the work lives in one place instead of a mailbox and a spreadsheet. The board follows progress on every project without chasing status by email.

SharePoint split up, permissions without a queue to IT

Industry and size:
Construction, 50 people
Starting point:
The whole company worked on a single SharePoint site, long past the size Microsoft recommends. Sync stopped keeping up and files went missing. Permissions were granted by hand, folder by folder, and the permission matrix was never up to date.
What we did:
We split SharePoint into smaller, ordered areas and rolled out Aclovo, our self service portal. Granting access moved from IT to the resource owners: an employee requests a folder, the owner approves, permissions are granted automatically.
Timeline:
1 month
Result:
The back office got back the time that used to go into permissions, and the permission matrix builds itself, with no spreadsheet to keep alive.

How a deployment runs

The same order whatever the platform. Cutover always outside working hours, and the old environment stays available until we confirm everything came across.

  1. 1 to 2 days

    Conversation and inventory

    We check what you have: accounts, licences, where files sit, who administers what. Without that, any plan is guesswork.

  2. 2 to 5 days

    Target design and quote

    We agree the structure of accounts, groups and permissions, the sign-in policy and which licences are genuinely needed. You get it in writing with a price.

  3. about a week

    Deployment with a pilot group

    We launch the environment for a small team. They work normally while we fix what only looked good on paper.

  4. evening or weekend

    Cutover for the rest of the company

    The remaining accounts move in a window outside working hours. In the morning the team starts in the new environment, not halfway through a migration.

  5. 1 to 2 days

    Training and handover

    We show the team how to work in the new environment and hand over the documentation. From there we can run administration on a monthly plan.

If the system is already in place, start with an audit

Atlassian instance audit

We go through Jira and Confluence: schemes, workflows, projects and spaces, permissions, Assets, Marketplace apps and licences. You get a report, a list of things to cut and a quote for the cleanup. If you order an optimisation project within 60 days, we deduct the price of the audit from its value.

  • Schemes and workflows
  • Project and space structure
  • Permissions and data visibility
  • Assets
  • Marketplace apps and licences
Time
3 working days
Price
up to 3,500 PLN net
Order an Atlassian instance audit

The terms we work on

The same terms apply to a one-off project and to a monthly plan.

PLN 2 million liability insurance

Our liability for damages is insured for PLN 2 million. A policy with a stated sum insured, not a reassurance given in a sales call.

No minimum contract term

We do not tie you into an annual contract or a lock-in period. One month’s notice applies from the first day, with no exit penalties.

Your environment, documented

We document the whole environment as we go and it belongs to you. When the partnership ends, we hand it over within 5 days and brief your next provider.

Access always stays on your side

Administrator accounts, domains and licences are registered to your company. Taking back control of the infrastructure needs neither our consent nor our help.

Predictable subscription

One fixed monthly rate. Work outside the subscription is quoted upfront and starts once you approve it, so nothing reaches the invoice that you have not agreed to.

One account manager and an SLA in the contract

You have an assigned account manager and you know them by name. Response times are written into the contract, from 15 minutes for critical incidents.

Tell us about your infrastructure

The first meeting takes 30 minutes and commits you to nothing. We will tell you straight whether we can help and what we would propose.

Wielkopolska · Poznań · Kalisz · Konin · all of Poland