Most companies run on these three platforms and that is usually where we start. We take them from deployment through migration to daily administration, and the other systems you run alongside come under the same care.
30-minute call · risk list within 1 business day · no obligation
Trusted by
We start with Microsoft 365, Google Workspace or Atlassian. The other systems you already run come under the same care.
Tenant, identity and permissions, mail, Teams and SharePoint, security policies and licences.
Domain and account configuration, shared drives, security rules and migrations between platforms.
Jira, Confluence, Jira Service Management and Assets: deployments, cleaning up inherited instances, migrations to Cloud.
One team runs all three platforms, so moving between them or working in a mixed environment does not require two suppliers. It does not stop there: the systems already running at your company come under the same contract. See the other systems we run
Six things clients ask about most often. We take each one from the decision to a working environment, and under every description there is a link to the page that goes into detail.
We set up the tenant or domain, move the accounts and configure password and sign-in policy. A Microsoft 365 rollout, formerly Office 365, or Google Workspace ends with a new joiner having mail, files and chat on day one.
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.
One account for everything, two-factor sign-in, groups instead of granting permissions one by one. We set up Entra ID or run your Active Directory so that someone leaving closes access everywhere.
Jira Service Management instead of a shared mailbox: service catalogue, queues and SLA. Every request has a number, an owner and a deadline.
Hardware, licences and dependencies in one model. A request lands on a specific asset, not in an empty description field.
We check what you pay for and what nobody uses. The plan follows how people actually work, not the price list.
Free preliminary review
Not sure where to start? A 30-minute call, and within one business day you get a list of risks in your company.
Because we work in your tenant and your instances. These are the problems companies bring most often, and how we close them.
3 days
“We have had Jira for years and nobody controls it.”
An audit of the existing instance takes from 3 business days. You get a list of what is still used, where permissions drifted, and what can be switched off. We move to the cloud only after that cleanup.
Weekend
“A mail migration means a day without work.”
We start the new environment with a small group. The rest of the accounts move in the evening or at the weekend. The old one stays until mail, calendars and files are confirmed in place.
One team
“Mail with one supplier, Jira with another.”
One team runs Microsoft 365, Google Workspace and Atlassian. A move between them, or a mixed environment, does not need two companies.
Your tenant
“When this ends we will be locked out of our own data.”
Accounts, domains and licences stay with your company. We work in your tenant, not ours.
PLN 2m
“Who pays if something goes wrong?”
Liability is insured for PLN 2 million. We sign a confidentiality agreement before the first login.
1 month
“I am afraid of being stuck with one company.”
Notice is one month, from day one. We hand over documentation and passwords within 5 business days.
Plus one owner of the systems, who knows the tenant and the history of changes. Not a hotline, and not a new person every time.
The three platforms above are the most common case, not the only one. Below are six examples from a much longer list: systems we run for clients from rollout and configuration through updates and daily upkeep.
Backup
Backup of servers, workstations and Microsoft 365 data. We set schedules and retention, and we test restores instead of assuming they work. We run it alongside Veeam and Synology arrays.
Privileged access monitoring
Control and session recording for administrators and external suppliers. You know who logged into a server, when and what they did there. Useful during audits and under NIS2.
Registers and workflows
Forms, registers and task flows where a spreadsheet has stopped being enough. We connect them to the other systems so the same data is not retyped by hand.
Access control and time tracking
Access control for rooms and working-time registration: cards, readers and permissions. We tie them to employee accounts so leaving the company also closes the doors.
Hardware keys for sign-in
Hardware confirmation of identity when signing in to Microsoft 365, Google Workspace and internal systems. A stolen password stops being enough and nobody retypes codes from a phone.
Remote desktop for the team
Access to applications running on a server, including older ones with no browser version. Cheaper than a separate terminal for everyone, with control over who signs in and from where.
This is not the full list and a missing name above settles nothing. We also run industry systems, ones inherited from a previous provider and ones the vendor no longer supports. Tell us what you use and what it has to do, and we will say whether we can take it on. What we do not know from real deployments we say straight away, instead of learning on your environment.
Migration is the most common reason companies come to us. Four scenarios we run regularly.
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.
Microsoft 365 to Google Workspace or the other way round. We map accounts, move mail and files, and keep addresses and aliases intact.
A migration plan, field mapping and removal of what stopped being used years ago. The Cloud instance starts without the inherited mess.
We move the service catalogue, queues and request history, and rebuild the support process where the old one did not work.
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.
The same order whatever the platform. Cutover always outside working hours, and the old environment stays available until we confirm everything came across.
We check what you have: accounts, licences, where files sit, who administers what. Without that, any plan is guesswork.
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.
We launch the environment for a small team. They work normally while we fix what only looked good on paper.
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.
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.
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.
A law firm guards the confidentiality of case files, an accounting office has to close the month on time, and a software house lives in Jira. See how we set the systems up in your industry.
Usually yes. Running a system means accounts and permissions, updates, backups, integrations and contact with the vendor, and that looks much the same whatever the name. We start by going through the documentation and how the system is wired into the rest of the environment. If we do not know something from real deployments, we say so before the contract, not after.
No. Mixed environments are the norm: mail in Microsoft 365, documents on Google Drive, tickets in Jira. We keep identity and access in one place so people have a single sign-in and leaving the company closes the accounts everywhere. We suggest a migration only when it genuinely simplifies the work or lowers licence costs.
It can, and that is usually where we start. An audit of an existing instance takes from three working days and ends with a list: which projects and schemes are still in use, where permissions have drifted from the organisation, what can be switched off. We migrate to Cloud only after the clean-up, so the mess does not travel with the data.
We do not schedule the switch for the middle of a working week. First we run the new environment for a small group, then we move the rest in the evening or at the weekend, and the old environment stays available until we have confirmed that mail, calendars and files are all in place.
Yes, and there is usually room for it. We check how many accounts are active, who has a higher plan than they need and what you are paying for twice after a system change. You get the recommendation with figures, and we change the plans only once you approve it.
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.
2019 - 2024 Interactive Workspace Ltd. - All rights reserved.