Category: Cloud

If your company virtualises with VMware, the renewal invoice has probably already caught you off guard, or it’s about to. Ever since Broadcom acquired VMware, the licensing model stopped being sold per product and in perpetuity and moved to subscription bundles. The practical outcome for many organisations is easy to sum up: you pay more, for things you may not even use, and with far less room to negotiate.

The good news is that today you have VMware alternatives for businesses that weren’t nearly this mature five years ago. The bad news is that migrating away from VMware on a whim, with no numbers and no plan, comes at a high price in outages and nasty surprises. Let’s get to what matters: what has changed, what real options you have and how to decide on merit rather than on headlines.

What has changed with VMware under Broadcom (and why it hits you even as an SME)

The underlying change isn’t a price tweak: it’s a change of model. Gone are the perpetual licences you bought once and kept running with a manageable annual support fee. Licensing now works by subscription and by bundle, with minimum contract sizes and a streamlined catalogue that pushes you towards packages full of features many SMEs never even touch. The general trend, acknowledged across the whole sector, is a significant rise in the cost of virtualising with VMware.

People tend to think this only hurts the big accounts, but it’s the other way round: the SME is the most exposed. It has no procurement team to fight it out with Broadcom, no volume to secure special terms, and no spare virtualisation engineer to rethink the platform. If you have three or four physical servers running vSphere holding up your ERP and your critical machines, the renewal can suddenly become one of the most expensive lines in your IT budget.

And here’s the mistake we see every day: renewing on autopilot “because it’s always been VMware”, without putting on the table how much it costs to stay versus how much it costs to move. That decision, taken without data, is the one that truly costs you dearly.

Your real options: stay put, switch hypervisor or move to the cloud

Before you commit to any of them, be clear that there is no one-size-fits-all answer. There are three paths, each with its own price and its own small print. No dogma.

1. Keep paying for VMware

Staying is no foolish choice if your platform is large, deeply integrated (vSAN, NSX, automation, DR built on VMware tooling) and a migration would put critical services at risk. Pro: zero migration, you stick with what you know, vendor support. Con: you swallow the price hike and tie yourself to Broadcom’s subscription model for years to come. It’s valid, but as a conscious decision, not out of inertia.

2. Migrate to another hypervisor (Proxmox, Hyper-V and the like)

Proxmox VE has become the standout alternative for SMEs: KVM-based virtualisation, containers, clustering, high availability and snapshots, with no per-CPU licences and a very reasonable optional support subscription. Pro: heavy savings on licences, no lock-in, a huge community. Con: your team has to learn it, or lean on a partner who already knows it inside out.

Hyper-V fits beautifully if you already live in the Microsoft world (Windows Server, Active Directory, Datacenter licensing). Pro: native integration and the backing of a giant. Con: it comes with its own cost model too and ties you to the Microsoft ecosystem. There are more options —KVM-based, Nutanix, XCP-ng— but for most SMEs the honest conversation starts with Proxmox or Hyper-V.

3. Move workloads to the public cloud

Moving machines to AWS, Azure or a managed cloud isn’t always “getting servers off your hands”: sometimes it’s swapping a hardware cost for an operating cost that, poorly sized, works out more expensive. Pro: you get rid of the metal, scale whenever you want and outsource the physical layer. Con: the recurring spend spirals if you don’t keep consumption in check, and not every workload fits in the cloud. Very often the winning answer is hybrid: the critical and stable on your own hypervisor, the elastic in the cloud.

How to decide well: 3-year TCO, criticality, effort and support

The decision isn’t made on what next year’s licence costs, but on the total cost of ownership (TCO) over three years. That takes in everything: licences, support, migration hours, team training, hardware and the month-to-month management hours. A “free” hypervisor that forces you to triple your administration effort isn’t free.

Four variables shape the outcome:

• 3-year TCO: compare “staying” against “migrating” with every cost included, not just the licence bill.
• Workload criticality: which machines bring the business to a halt if they fail, and how much downtime you can genuinely tolerate.
• Migration effort: number of VMs, dependencies, integrations with backup and with your storage array.
• Support: who picks up the phone at three in the morning when something goes down, and how quickly.

Migrating to save on licences only to end up spending twice as much on management hours isn’t a saving: it’s just moving the problem somewhere else.

Our recommendation is a cold one: put the numbers down scenario by scenario. Almost always a clearly better option emerges for your case. And if it doesn’t, the wisest move may be to renew VMware for one more cycle while you prepare the migration calmly. Both are valid answers as long as they’re backed by data.

How to migrate without surprises: inventory, testing, cutover window and rollback

A well-run hypervisor migration is boring, and that’s exactly what you want. The drama shows up when someone starts moving machines “to see what happens”. The method that keeps surprises at bay has four clear phases:

• Inventory and dependencies: every VM, its resources, its connections and what depends on what. Whatever isn’t inventoried is exactly what breaks.
• Testing in a lab environment: you migrate non-critical machines first, validating performance, networking and backups on the new platform before you touch production.
• Controlled cutover window: you move the critical workloads at an agreed time, with the migration rehearsed and the timings measured, not improvising on a Sunday.
• Rollback plan: a tested rollback and an untouched copy of the original environment. If something goes wrong, you return to VMware and try again another day, with no data loss.

And one detail many forget: the migration doesn’t end when the last VM boots on the new hypervisor. It ends when you have 24/7 monitoring and verified backups running on the new platform. Before that, you haven’t migrated: you’ve moved the risk to a place you don’t yet control.

The MagicBoxDesk offering: managed virtualisation and cloud

At MagicBoxDesk we’ve spent years building and migrating virtualisation platforms, and this is exactly the decision where a company saves —or wastes— a lot of money depending on how well advised it is. That’s why we don’t sell you a specific hypervisor: first we look at your numbers and then we tell you what suits you, even if sometimes that means sticking with VMware for one more cycle. You can take it on as a fixed-scope project (audit and migration at a fixed price) or as an ongoing managed service with a monthly fee and no surprises, within our infrastructure and cloud services.

What the service includes:

• Audit of your current environment: a real inventory of VMs, licences, dependencies and what your VMware costs you today.
• A proposal with the numbers: 3-year TCO comparing staying, switching hypervisor or moving to the cloud. You decide on data, not on hunches.
• Managed migration: lab testing, an agreed cutover window and a tested rollback plan. No surprise outages.
• Ongoing support and 24/7 monitoring on the new platform, with verified backups. You forget about the metal.

The advantage of outsourcing your IT with us is simple: you gain a platform that’s cheaper to run, with no lock-in and with someone who answers when something fails. A managed service for businesses that turns the VMware price hike into an opportunity to put your infrastructure in order, rather than an annual scare.

Turn the VMware price hike into a smart decision

Broadcom’s licensing doesn’t have to be bad for your company: it can be the nudge you needed to rethink an infrastructure that had been on autopilot for years. But that only happens if the decision is made on merit and with numbers, not in the rush of a renewal.

At MagicBoxDesk we audit your VMware, lay out the scenarios with the figures and, if migrating makes sense, we handle it from start to finish so you can get on with your business. Ask for a no-obligation quote and we’ll tell you what really suits you; if you’d rather, drop us a line or give us a call and we’ll look at it together.

Microsoft has raised the price of its Microsoft 365 plans again and, along the way, reshuffled the line-up: plans that change names, features that move around, and add-ons that used to be included and are now billed separately. The typical company reaction is to pay the new invoice and carry on. That is the most expensive mistake of all.

Because most companies don’t overpay because of Microsoft: they overpay because nobody has reviewed their licensing in years. Licences assigned to people who have already left, premium plans for profiles that only use email, add-ons that duplicate what was already included. A price rise is, in reality, the best excuse you’ll ever get to clean house and cut your Microsoft 365 costs without losing a thing. Let’s get to it.

Why almost every company overpays for Microsoft 365

Microsoft 365 licensing is quick to sign up for and slow to forget. You buy licences to get started, the company grows, people come and go, and nobody ever looks at the list again. The result is an invoice that climbs on its own, and not just because of Microsoft’s prices. These are the three leaks that show up in almost every audit.

The first is unused licences. Accounts assigned to employees who have moved on, to a summer intern, to a project that closed months ago. The licence stays alive and keeps billing month after month, because offboarding someone almost never includes freeing up their plan. In a workforce with turnover, that’s hundreds or thousands of euros a year spent on empty chairs.

The second is the oversized plan. A powerful plan was signed up for “to have everything covered” and rolled out identically to the entire workforce. But the warehouse operator who only clocks in and checks email doesn’t need the same plan as the finance director. Paying for the most expensive plan across 100% of your people when half of them use 10% of its features is throwing money away with style.

The third is duplication: add-ons and services you pay for separately when they already come bundled with your plan. Extra storage, a security tool, a third-party video-calling solution… that your own Microsoft 365 already covers. They pile up because each one was signed up for at a different moment and nobody has the full picture.

Your Microsoft 365 invoice doesn’t grow because your company grows. It grows because nobody is watching it.

How to audit your licensing (without guessing)

Optimising isn’t “buying the cheapest plan”. It’s matching every licence to a real person and a real need. That takes a methodical audit, not a hunch. These are the four cross-checks you need to run.

• Real users vs. licences purchased. The first number that surprises everyone: how many licences you pay for versus how many people actually work here today. That gap is usually pure money.
• What each profile needs. Group your workforce by real usage: who needs the desktop apps, who works only in the browser, who does nothing but check email. Not everyone needs the same thing, and that’s where the saving lives.
• Mailboxes that don’t need a licence. Addresses like info@, sales@ or support@ can run as shared mailboxes, which are free and consume no plan. If you have them set up as licensed users, you’re paying for a mailbox that shouldn’t cost anything.
• Ex-employee accounts. Review who’s actually active. Plenty of accounts belonging to people who left long ago stay licensed “just in case” to keep their email, when that content can be archived without keeping the licence alive.

With those four cross-checks on the table you have the map: you know how much you pay, why, and how much of it is surplus. It’s exactly the kind of work we do when we manage a company’s infrastructure and workplace, because the licence is only the tip of the iceberg of your real IT cost.

The savings levers that actually work

Once the audit is done, the saving materialises through concrete actions. These aren’t tricks: it’s assigning what you already pay for correctly and stopping paying for what you don’t use.

Match the plan to each profile. Downgrade anyone who doesn’t tap into the premium features and keep the powerful plan only where it earns its keep. Multiplied across the whole workforce, changing the plan for a third of your users is the lever that moves the invoice most. The key is to do it by profile, not across the board.

Annual commitment vs. monthly. Microsoft charges a premium for the flexibility of paying month by month. If your core headcount is stable, committing those licences for a year cuts the unit price. The clever tactic is to combine the two: a stable base on an annual commitment plus a small monthly buffer for peaks and temporary hires. That way you save without locking yourself in.

Drop unnecessary add-ons and use what’s included. Before renewing any third-party tool, check whether your plan already covers it. Storage, video calls, basic security, device management… Microsoft 365 includes far more than most companies ever switch on. Paying twice for the same feature is the most common duplication, and the easiest to cut.

The balance: saving without cutting security short

Here comes an important warning, because optimising badly is dangerous. Trimming licences to save is fine; trimming security to save is a mistake that can cost you a thousand times what you save. And it’s a real temptation: some of the features billed separately or bundled into the higher plans are precisely the protective ones.

Don’t touch what protects your company. Multi-factor authentication (MFA) is non-negotiable and is largely available even on the basic plans: there’s no excuse for having it switched off. The Defender layers —anti-phishing, email and endpoint protection— aren’t a dispensable luxury when ransomware arrives by email every single day. Downgrading a user who just checks email is fine; leaving your entire company without anti-phishing filtering to save a few euros is opening the door.

The right goal is to pay for what you use and protect what matters. Real optimisation is knowing where to cut (oversized plans, dead licences, duplicated add-ons) and where not to touch a single euro (identity and security). That line is exactly what separates a smart saving from a future problem, and it’s where having someone with judgement makes the difference. If you already have a managed IT maintenance service, the licensing review should be part of it.

What MagicBoxDesk offers: Microsoft 365 optimisation and management

At MagicBoxDesk we do this for you, with the numbers on the table. We don’t sell a generic report: we audit your actual licensing, show you exactly how much is surplus and carry out the change. And we don’t stop there: we manage your Microsoft 365 on an ongoing basis so the invoice doesn’t quietly inflate itself again every time someone joins or leaves. It’s the natural way to outsource your IT without losing control of the spend.

• Full licence audit: real users vs. licences, usage profiles, shared mailboxes, ex-employee accounts and duplicated add-ons.
• Savings proposal with real figures: what you pay today, what you’d pay optimised and exactly what changes. You decide with data, not promises.
• Reallocation carried out: we change plans by profile, free up what’s surplus and switch on what you already have included, with no outages or data loss.
• Ongoing management: onboarding and offboarding, regular licensing reviews and security (MFA and Defender) always in place. A monthly fee with no surprises.

You take it on as a managed service for businesses, with a clear monthly fee, and what you gain is twofold: a lower Microsoft 365 invoice and the peace of mind that someone is watching it for you. In most cases, the saving pays for the service several times over.

If the latest price rise has made you look at the invoice with fresh eyes, now is the moment to do the maths properly. Request a no-obligation quote and we’ll tell you how much you can genuinely save on your licences, with concrete figures and without touching your security. You can also get in touch and we’ll go through it with you.

Cloud bills almost never spiral out of control overnight. They creep up little by little, month after month, until one day someone in finance asks why you’re paying the equivalent of a part-time salary. And the honest answer is usually uncomfortable: we don’t know exactly. That’s where the real problem starts, and it isn’t the cloud itself, but the lack of control over what gets switched on, what gets forgotten and what nobody ever switches off.

The good news is that cutting cloud costs doesn’t mean sacrificing power or accepting that your website will run slower. Almost all the savings sit in money you’re already throwing away without anyone noticing: oversized machines, test environments left running all weekend, orphaned disks from servers you deleted six months ago. This is what’s known as FinOps, and applied sensibly to a small business it hands you back between 20% and 40% of the bill without touching performance. Let’s break it down.

Why the cloud bill spirals out of control

The cloud is sold with a perfect promise: you only pay for what you use. The small print says something else: you pay for what you have switched on, whether you use it or not. And switching on is trivial —two clicks— while switching off requires someone to remember, to know that resource is theirs and to have the time. In a small business without a clear cloud owner, that “someone” doesn’t exist, so nothing ever gets switched off.

On top of that comes the “just in case” culture. A developer spins up a machine bigger than necessary because they don’t want to fall short. More storage than you’ll need in two years gets bought. Environments are duplicated for a demo and left there. Each decision, on its own, looks reasonable. Added together, they’re a constant leak that the bill hides behind a single global figure nobody breaks down.

The third factor is the complexity of the pricing model. AWS, Azure and Google Cloud have catalogues with thousands of items, charges for data transfer, and rates that vary by region. It’s almost impossible for anyone without dedicated time to understand where the money goes. And what isn’t measured can’t be controlled. That’s why the first step in any serious optimisation isn’t switching anything off, but actually seeing the bill: by service, by project and by owner.

Switched-off, oversized and forgotten resources

This is where the bulk of the quick savings lives, the kind that requires no redesign at all. There are three types of waste that show up in almost every account we audit, and they’re fixed in days, not months.

• Orphaned resources: disks that outlived the machine you deleted, unused static IPs, backups of servers that no longer exist, load balancers with nothing behind them. They serve no one and you pay for them in full every month.
• Oversized resources: the 16 GB RAM machine that always runs at 8%. The database engine provisioned for peaks that never arrive. Adjusting to the real size (rightsizing) usually cuts that resource’s cost in half without the user noticing any difference.
• Resources running unused: development, test and staging environments running 24/7 when they’re only used during office hours. Switching them off at night and on weekends removes 70% of their bill in one go.

That last point is the easiest win and the one most people ignore. A test environment only needs to be up 40 hours a week, not 168. Scheduling an automatic shutdown outside working hours is half an hour of work and saves money every week for years. The same goes for lifecycle policies: moving old data to cheaper tiers and automatically deleting whatever expires.

The prerequisite for all of this is tagging. If every resource carries its project, its environment and its owner, you know what you can switch off without fear. Without tags, every cleanup is Russian roulette where the prize is taking down production. It’s what turns optimisation into something repeatable instead of a one-off feat of heroics.

Reservations, autoscaling and well-tuned licences

Once you’ve cleaned up what’s surplus, it’s time to optimise what you actually need. And here the most expensive mistake is paying full list price for workloads that are perfectly predictable. If you know a server will be up all year long —and your production database is— paying for it on demand is throwing money away.

Reservations and savings plans for the stable stuff

Reserved instances and savings plans give discounts of between 30% and 70% in exchange for committing to a certain usage for one or three years. For the foundation of your infrastructure —the part you know will still be there— it’s free money you’re turning down. The key is to reserve only what’s genuinely stable and leave the rest on demand; over-committing ties you to resources you might stop using.

Autoscaling for the variable stuff

For workloads that rise and fall —your website during a campaign, a process that spikes at month-end— the answer isn’t a huge machine just in case, but autoscaling: letting the infrastructure grow when needed and shrink once the peak passes. That way you pay for high capacity only during the hours you use it, and performance doesn’t suffer because the system reacts before the user notices. This dismantles the false dilemma between saving and performing: set up properly, you do both at once.

Licences you pay for twice

And then there’s the silent chapter: licences. Windows Server, SQL Server or commercial databases billed inside the cloud machine when you may already own licences you could bring, or when an open source alternative would do the same job for free. Reviewing this once a year recovers surprising amounts, because it’s money paid on autopilot.

How to keep an eye on it every month without going mad

Optimisation isn’t a one-off project. If you abandon it, within six months the bill inflates again because the team keeps creating resources and nobody reviews them. But that doesn’t mean living glued to dashboards: it means setting up three or four automatic controls that work for you and only alert you when something drifts.

• Budgets with alerts: you set a monthly cap per project and get a warning when projected spend is about to exceed it. You find out mid-month, not when the bill arrives.
• Anomaly detection: the three big providers alert you when spend spikes in an unusual way. A runaway process burning resources can cost hundreds of euros over a weekend if no one spots it.
• A 30-minute monthly review: a look at the breakdown by service compared with the previous month. What went up and why? With tagging done properly, the answer is one click away.
• Recommendations report: the platforms suggest what to rightsize and what to reserve. Don’t accept it blindly, but it’s your starting point every month.

The key is to lean this oversight on your usual monitoring, so you can cross-reference cost with real performance. There’s no point trimming a machine if it degrades the service: the goal is to spend just enough for the performance your business needs. Cost and performance are always looked at together.

The cloud isn’t expensive. What’s expensive is the cloud nobody watches.

How MagicBoxDesk helps you optimise your cloud

At MagicBoxDesk this is exactly what we do: we audit your cloud account thoroughly and show you, in euros, where the money goes and how much we can recover without touching your performance. First the quick cleanup, then the fine-tuning of reservations, autoscaling and licences, and finally we leave the monitoring system in place so the bill doesn’t spiral out of control again. All part of our managed cloud infrastructure services, with support across Spain and on-site visits to your offices when needed.

The best part is that cloud optimisation almost always pays for itself: the first month’s savings usually cover the work, and from there it’s margin for your business. We take care of everything so you can focus on what you do best. Ask for a no-obligation quote and, with your real bill in front of us, we’ll tell you how much you can genuinely save.

Migrating a company to Microsoft 365 doesn’t fall apart for lack of licences: it falls apart because someone switches off the old email too soon and on Monday morning half the workforce can’t send a single message. The technology is the easy part. The hard part is doing it without anyone noticing the change, and that’s where the clean migrations part ways from the ones that end in a week of firefighting.

This guide gets straight to the point: what really changes, how you prepare the ground, how you move the email without cutting it off, the mistakes that cost you dearly, and what needs doing the day after. If you want to do it with a safety net, at the end we tell you how we handle it without stopping your business.

What you gain (and what changes) by moving to Microsoft 365

Microsoft 365 isn’t “the same old Office but in the cloud”. It’s no longer having to maintain your own mail server, having your mailbox accessible from any device, and unifying email, files, video calls and security under a single identity. For an SME that means less infrastructure to look after and fewer things that can break at six o’clock on a Friday.

What you gain, specifically:

• Professional email with your own domain, with no physical server to maintain or update.
• Files in SharePoint and OneDrive: goodbye to the shared NAS folder only one person understands.
• Teams for meetings and teamwork, using the same login as your email.
• Security built in: MFA, access policies and Microsoft’s cloud backup.

What changes for the user? Less than they fear. Outlook is still Outlook. What changes is underneath: where the mailbox lives, how it’s accessed and who answers when something goes wrong. And the bill changes: you move from an investment in servers to a predictable per-user fee that scales up and down as your team grows or shrinks.

Preparation: domain, licences and a backup first

90% of a migration’s success is decided before a single message is moved. This phase is boring and it’s the one nobody wants to pay for; it’s also the one that prevents disaster. Three pillars.

1. The domain and its DNS

Your domain is what sends email to one place or another. Before migrating you have to verify the domain in Microsoft 365 and be clear about the DNS records: MX (where the email arrives), SPF, DKIM and DMARC (which say who is allowed to send on your behalf). Changing the MX record is what redirects email to the new mailbox, and that’s why you touch it at the end, not at the start. Change it too soon and you start receiving into an empty mailbox.

2. The right licences

Not every licence does everything. Business Basic gives you email and Teams on the web but no desktop Office; Business Standard does; Business Premium adds the security layer (Intune, Defender) that many companies need and don’t even know exists. Buying wrong here means overpaying every month for years, or falling short and having to upgrade in a hurry. You size it by user profile, not by buying the same thing for everyone.

3. The backup first (this is not optional)

Before moving anything, you back up the email, contacts and calendars from the source. It seems obvious and it’s the first thing anyone in a hurry skips. A migration goes well 95% of the time; the backup is your insurance for the remaining 5%. Without a backup, a sync error means lost email with no way back.

The migration step by step without cutting off the email

The key to not stopping the business is simple to state and hard to execute: the new mailbox is filled before email is redirected to it. Never the other way round. That way, on switchover day the user already has all their history waiting for them. The order that works:

• Preparation: domain verified, users and licences created in 365, backup done.
• Initial sync: all the email from the old system is copied to the new mailbox in the background, without touching the live email. The user carries on working as normal.
• Delta sync: just before the cutover, only the new emails from those last few hours are copied. That way the new mailbox is up to date to the minute.
• MX change: the MX record is pointed to Microsoft 365. From here on, new email arrives in 365. You pick a low-traffic window (Friday evening or the weekend).
• Reconfiguring clients: Outlook and mobiles point to the new mailbox. With the sync done properly, the user opens Outlook on Monday and it’s all there.

While the DNS propagates (which can take hours) some email may still reach the old mailbox. That’s why the source mailbox isn’t switched off the same day: it’s kept alive for a few days catching the stragglers. Email is never lost because there’s always a mailbox listening.

Common mistakes that cost you dearly

Almost every migration that ends badly fails for the same reasons. None of them is a complex technical problem; they’re all about method.

• Changing the MX before syncing. The classic: you redirect email to an empty mailbox and the user panics because “everything’s gone”.
• Switching off the old server too soon. You lose the emails that were still arriving there during DNS propagation.
• Forgetting SPF, DKIM and DMARC. You migrate and suddenly your outbound email lands in spam at your clients’ end. Silent reputational damage.
• Not accounting for printers, scanners and applications that send email. The multifunction device that “scans to email” stops working because nobody reconfigured its SMTP sending.
• Not warning the team. With no heads-up beforehand and nobody to ask, every question turns into a ticket and lost hours.
• Migrating without a backup. Working without a net. When something fails, there’s no way back.

A migration is judged by what the user doesn’t notice. If nobody writes to you on Monday asking where their email is, it went well.

After migrating: security (MFA) and training the team

Moving the email is half the job. The other half begins once everything’s in 365, and it’s the half that separates “we have Microsoft 365” from “we’re protected with Microsoft 365”.

First, MFA (two-step verification) for everyone, no exceptions. A cloud mailbox with only a password is a mailbox that sooner or later ends up compromised: phishing exists precisely because it works. With MFA on, stealing the password is no longer enough to get in. It’s the security measure with the best effort-to-protection ratio there is, and in 365 it’s switched on by policy. From there it’s worth reviewing access by device, blocking automatic external forwarding and setting a sensible password policy.

Second, minimal training for the team. Not a three-day course: four practical things. Where the shared files are now (SharePoint instead of the network folder), how the second factor works on the phone, how to recover a deleted email and who to call when something isn’t working. A technically perfect migration that leaves the team lost ends up generating more tickets than an average one done with proper support.

How MagicBoxDesk does it with no downtime

At MagicBoxDesk we migrate companies to Microsoft 365 across Spain with one non-negotiable principle: the business doesn’t stop. We prepare the ground (domain, DNS, licences sized to each profile, a full backup first), we sync the mailboxes in the background while your team keeps working, and we leave the MX change for the lowest-impact window. On Monday, everyone opens Outlook and finds their email, contacts and calendar intact. No outages, no lost email, no surprises.

And we don’t leave you on your own the day after: we switch on MFA and the security policies, reconfigure printers and applications that send email, train the team and stay on as your outsourced IT department for whatever comes next. It’s part of our infrastructure and cloud services, designed so technology stops being your problem and you can get on with your business.

Thinking about making the jump to Microsoft 365, or dragging along a half-finished migration that left problems behind? We’ll review it and tell you what you really need, no smoke and mirrors. Request a no-obligation quote and we’ll plan your migration without stopping the business.

The question almost nobody asks before paying for Microsoft 365 Copilot is the only one that matters: which specific task will someone on your team stop doing, or do in half the time? Copilot is neither magic nor a demo toy. It’s a layer of generative AI inside Word, Excel, Outlook, Teams and the rest of the suite, with a per-user paid licence on top of the one you already have. And its value doesn’t come down to the AI model: it comes down to how well organised your data and your permissions are.

This guide gets straight to the point: what Copilot really does, the requirement no salesperson mentions, when it’s worth paying for, how to measure the return and how to roll it out without opening a security hole. And if you want it done properly, we’ll tell you how we set it up.

What Copilot really does day to day (and what it isn’t)

Copilot lives inside the apps your team already uses and works on your own documents, emails and meetings, not on generic internet knowledge. That’s the difference from any old ChatGPT: it knows what’s in your SharePoint, your inbox and your Teams, and it uses that to draft, summarise and search. Here’s where it genuinely saves time:

• In Outlook: it drafts replies, condenses a twenty-email thread into three lines and tells you what people are actually asking of you.
• In Teams: it summarises a meeting you missed, pulls out decisions and action items with owners, and brings you up to speed on a long chat.
• In Word: it turns four bullet points into a first draft proposal, rewrites in a different tone or summarises a twenty-page contract.
• In Excel: it explains a table, suggests formulas and spots trends without you wrestling with the syntax.

And now what it isn’t, because this is where nearly every disappointment starts. Copilot doesn’t replace anyone: it speeds up people who already know how to do their job. It isn’t infallible; it makes things up from time to time, so everything has to be checked before it goes out. And if your data is a mess, its answers will be a tidy mess. It isn’t an “install it and you’re done” either: without the groundwork that comes next, you pay for the licence and people abandon it within two weeks.

The requirement nobody tells you about: data governance and permissions

This section decides whether Copilot is a tool or a security incident waiting to happen. The rule is as simple as it is uncomfortable: Copilot sees exactly what the user using it sees. No more, no less. It respects the permissions in your SharePoint, your OneDrive and your mailboxes to the letter. The problem isn’t Copilot: it’s that in most companies those permissions have been wrong for years and nobody noticed.

Think of it this way. That “Management” folder with the payroll that someone shared with “the whole organisation” as a quick fix. The salary spreadsheet sitting in a shared location. As long as nobody browses their way there, they’re “hidden in plain sight”. Copilot changes the rules: an employee types “how much does the sales team earn?” and if they have technical permission to read that file —even though they never should have— it serves it up, summarised, in seconds. They haven’t hacked anything: they’ve used a permission that was wrong from the start.

Copilot doesn’t create security holes: it makes them visible. It turns every misconfigured permission from the last ten years into a question anyone can ask.

That’s why rolling out Copilot properly begins before you buy a single licence, with a review of permissions and data governance: who accesses what, where folders are open to too many people and which sensitive information needs labelling or restricting. It’s a job for cybersecurity before it’s a job for AI, and skipping it turns a good idea into a compliance and GDPR problem.

When it’s worth it and how to measure the return

Copilot is a per-user paid licence on top of what you already pay for Microsoft 365. It isn’t cheap multiplied across your headcount, so the question isn’t “do I want it?” but “which roles give me back more than it costs?”. And the answer is measured in hours of expensive staff no longer lost to repetitive tasks.

It clearly pays off in roles that live in the suite and produce a lot of text or analysis:

• Management and middle managers drowning in email and meetings: thread summaries and automatic minutes.
• Sales and marketing: first drafts of proposals, quotes and communications that are then fine-tuned by hand.
• Administration, legal and finance: contract summaries, data cross-referencing and repetitive documents.
• Support and customer service: faster, more consistent replies drawn from internal documentation.

It pays off little in roles that barely touch Office: production, warehouse, workshop or anyone who lives in their own vertical software. Buying Copilot for the whole workforce “in the name of fairness” is the fastest way to throw money away. It’s assigned by role and by task, not in bulk.

How do you measure the return without kidding yourself? Before deploying, pick a pilot group and define which specific task you want to speed up and how long it takes today: preparing a proposal, writing the weekly minutes, answering the morning email. Give it Copilot for a month and measure that same task again. If one person saves two or three hours a week on real work, the licence pays for itself with room to spare. If a month in people don’t even open it, it’s not that Copilot doesn’t work: it’s that the use case didn’t fit, and that’s fixed before you scale to everyone else.

How to roll it out well: assessment, permissions, piloting, training and deployment

A rollout that works looks nothing like “buy licences and hand them out”. It follows an order that avoids the two ways to fail: the security hole and abandonment through lack of use. Five phases.

• Assessment: which roles genuinely benefit, which tasks you want to speed up and the state of your data and your current Microsoft 365 licensing.
• Permissions clean-up: auditing and fixing access in SharePoint, OneDrive and Teams, closing folders that are open to too many people and labelling sensitive information. The non-negotiable phase.
• Piloting: a small group, with defined use cases and a baseline measurement. You learn what works in your company without risking the whole workforce.
• Training: teaching people to ask well (the “prompt” matters), to always check the answer and not to feed Copilot anything that shouldn’t leave the building. Without this, people give up on it.
• Deployment in waves: you scale from the pilot to everyone else group by group, matching licences to each role and with support to answer questions on the spot.

Note the order: security comes before AI, and piloting before mass deployment. It’s the opposite of buying licences for everyone on day one and discovering a week later that an intern can look up management’s payroll. Doing it right isn’t slower: it saves you having to pull the plug on the project in a panic.

What MagicBoxDesk offers: Copilot and AI in the workplace, properly implemented

At MagicBoxDesk we implement Microsoft 365 Copilot and AI in the workplace as a managed service, not as a licence sale and goodbye. We start with your data and your permissions, and we don’t switch Copilot on until the ground is safe. We work across the whole of Spain, remotely and on site, and we stay on as your outsourced IT department. Here’s what’s included:

• Permissions review and data governance across SharePoint, OneDrive and Teams before activating anything: we close the holes Copilot would expose.
• Optimal licensing: Copilot only in the roles where it repays the investment, with the right Microsoft 365 plan underneath. Neither too much nor too little.
• Piloting with real metrics: one group, defined use cases and before/after measurement to know whether it pays off before scaling.
• Practical training for your team: asking well, always checking and using the tool with a security mindset.
• Ongoing support as a managed service, with a flat monthly fee and no surprises, to answer questions and fine-tune the rollout.

We do it as part of our managed workplace service and the rest of the IT services that companies across Spain use to outsource their IT department. The advantage of having MagicBoxDesk handle the rollout is simple: AI enters your company delivering real value without opening a security flank.

Thinking about Copilot and not sure whether it’s worth it, or want to set it up without leaking information along the way? We’ll review it and tell you what you genuinely need, no fluff. Request a no-obligation quote and we’ll plan a Copilot rollout that’s secure, measured and profitable.

An Exchange mail server that has stopped receiving patches isn’t “a slightly old server”: it’s an open door with your name written on it. The older versions of Exchange Server (2016 and 2019) have reached end of support, and that means one very specific thing: Microsoft no longer publishes security updates for them. The next serious vulnerability that turns up won’t be patched. And on a mail server, they do turn up.

The good news is that getting out of there doesn’t have to hurt. Most SMEs come out ahead by moving their email to the managed cloud, and it can be done without losing a single email and without any downtime. This guide explains why it’s urgent, what your real options are and how to migrate without your team noticing a thing. At the end we tell you how we do it.

Why an unsupported mail server is a serious problem

Email is the most exposed system your company has: it’s published on the internet 24 hours a day, seven days a week, waiting for connections from anyone. When Microsoft stops supporting a version, it stops plugging the holes that keep being discovered. An unsupported mail server piles up known flaws that nobody is ever going to fix, and attackers hunt for them there precisely because they know plenty of companies are still running the old version “because it works”.

The risk isn’t theoretical, and it has three faces that cost real money:

• Security: Exchange has been one of the favourite targets for attacks in recent years. An unpatched server is the perfect way in for ransomware, data theft or full control of your corporate email.
• Reputation and spam: if they compromise your server, it starts sending spam in your name. Your domain ends up on blacklists and, all of a sudden, your legitimate emails bounce or land in your clients’ spam folder. Rebuilding a domain’s reputation takes weeks.
• Downtime: the day that server goes down —because of an encryption attack or a fault with no fix— your company is left with no email. And with no email you can’t invoice, look after clients or coordinate the team.

And one factor almost nobody looks at: compliance. Keeping personal data on a system you know to be insecure is hard to justify under the GDPR if there’s a breach. “It was doing the job” is not a defence.

Your options: Microsoft 365, another managed email service or an updated in-house server

There’s no single right answer for everyone, but there is one that fits the vast majority of SMEs. These are the three real ways out, with the criteria to choose between them.

1. Migrate your email to Microsoft 365 (the option that wins almost every time)

Moving to Microsoft 365 means no longer having a physical mail server to maintain, patch and watch over. The mailbox lives in Microsoft’s cloud, updates itself, comes with built-in security (MFA, anti-spam, cloud backup) and is paid for with a predictable per-user fee. For a company coming from on-premise Exchange, the change for the user is minimal: Outlook is still Outlook. What disappears is the infrastructure that breaks on a Friday afternoon. For most SMEs, this is the sensible call.

2. Another managed cloud email service

If your company doesn’t live inside the Microsoft ecosystem or you’re after something lighter, there are professional managed email platforms that also take the in-house server out of the equation. They cover email with your own domain, shared mailboxes, anti-spam and backup. It makes sense when you don’t need Teams, SharePoint or desktop Office and you just want solid email, nothing more. The key point is the same: that someone manages it and keeps it secure for you, rather than setting up another unwatched server.

3. Keep your own server, but up to date

Keeping Exchange in-house only makes sense in very specific cases: regulatory requirements that force you to keep email within your own premises, or legacy integrations that can’t be moved. And even then, the condition is non-negotiable: a supported version, patched and up to date and monitored. Staying on an unsupported version “to save money” isn’t saving: it’s putting off a much bigger bill.

What’s at stake for your company in an email migration

Email isn’t just the new messages coming in. It’s years of relationship history with your clients, and plenty of people use it as their working archive. A botched migration doesn’t “lose a couple of emails”: it can lose contracts, quotes you sent, legal conversations or the one place that attachment you now need was stored. That’s why an email migration is judged by what does not get lost.

What has to be carried across in full, without a single gap:

• Complete mailboxes: all the email, with its folder structure exactly as it is, not a jumbled dump.
• History, contacts and calendars: years of correspondence, the contacts address book and the future meetings already booked in.
• Rules, signatures and auto-replies: the filters each person had set up and the corporate signatures, so nobody has to redo them by hand.
• Distribution lists and shared mailboxes: the “info@”, the “accounts@” and the internal lists the whole team relies on.
• Service continuity: throughout the entire process, the company keeps sending and receiving. No “no email today” window.

An email migration is judged by what the user does not notice. If on Monday nobody asks where their history has gone, it went well.

How to migrate with no downtime

The golden rule is easy to state and hard to pull off: the new mailbox is filled before email is redirected to it, never the other way round. That way, on switchover day, everyone already has their history waiting for them. The process that works, in phases:

• Coexistence: the old system and the new one run side by side for a few days. Email keeps arriving in Exchange while the destination is prepared and a prior backup is made.
• Batch migration: mailboxes are copied in the background, in groups, without touching the email in production. The team keeps working like any other day while the destination fills up.
• Final sync: just before the cutover, only the emails from the last few hours are copied, so the new mailbox is up to the minute.
• MX switch: the domain’s MX record is pointed at the new email service, in a low-traffic window (Friday evening or the weekend). From then on, new email arrives in the cloud.
• Verification: we check that email arrives and goes out, that SPF, DKIM and DMARC are right (so you don’t land in spam), that the printers and applications that send email still work, and that nobody has been left stranded.

The old Exchange server is not switched off on the same day: it’s kept alive for a few days, collecting any email that still comes in while DNS propagates. There’s always a mailbox listening, so no email falls through the cracks. Once everything is verified and stable, the old server is retired safely.

The MagicBoxDesk offer: your email migration, managed end to end

At MagicBoxDesk we take your email off the unsupported server and move it to the cloud anywhere in Spain, with one non-negotiable principle: the business doesn’t stop and not a single email is lost. We do it as a managed migration on a fixed-scope project —you know the scope and the cost upfront, no surprises— and, if you want, we stay on afterwards as your managed business email and your outsourced IT department. It’s part of our infrastructure and cloud services, with cybersecurity included from day one.

What the service includes:

• An upfront audit of your current Exchange and the choice of destination (Microsoft 365 or another managed email service) based on your real situation.
• Prior backup and batch migration with coexistence: mailboxes, history, contacts, calendars, rules, signatures, lists and shared mailboxes.
• MX switch and SPF, DKIM and DMARC configuration so your email gets through and doesn’t land in spam.
• Built-in security: MFA for everyone, access policies and safe retirement of the old server.
• Team training and ongoing support on a monthly fee with no surprises if you choose to have us keep managing your email.

What you gain is what matters: zero downtime, zero lost emails and email that is no longer a security risk, but a tool that works. You stop watching patches and praying that the server holds out.

If you’re still running an unsupported Exchange, every week that goes by is a week of free exposure for attackers. Let’s sort it out before it becomes an emergency. Ask for a no-obligation quote and we’ll plan your email migration without stopping the business.

The question “do we move to Azure, to AWS, or do we build our own server?” is almost never decided on technology. It’s decided on badly calculated money, on a fear of losing control, and on a sales rep who showed you a pretty demo. And that’s how an SME ends up paying a cloud bill three times higher than expected, or buying a rack of servers that will be depreciating obsolescence within three years.

The short answer: there’s no winning option in the abstract. There’s a right option for your workload, your growth forecast and your tolerance for managing hardware. Let’s do the sums that almost nobody does properly and give you the judgement to decide with your head, not with the brochure.

Public cloud vs. your own server: the real decision

Forget “Azure vs AWS” for a moment. That’s the second question. The first is public cloud or your own infrastructure, and these are two opposing business models disguised as a technical decision.

The public cloud (Azure, AWS and also Google Cloud) is renting by usage: you pay for compute, storage and traffic based on what you consume, you scale in minutes and you buy nothing. Your own server —physical, in your office or in a data centre (colocation)— is an investment: you put the money up front, the hardware is yours and the marginal cost of using it more is close to zero. One turns capital expenditure into operating expenditure; the other does exactly the opposite.

Between Azure and AWS, for an SME the real difference is smaller than it seems. AWS is the most mature, with the broadest catalogue of services; if your project is technical, with custom development or heavy automation, you’ll fit in well. Azure wins when you already live in the Microsoft ecosystem: if you use Microsoft 365, Active Directory and Windows Server, integration with Entra ID, unified identity and hybrid licensing save you friction and sometimes money. The Azure vs AWS decision usually comes down to where your company already is, not to which cloud is “better”.

Cost over 3 years: the sum nobody does properly

This is where most decisions are lost. The honest comparison isn’t “cloud monthly fee” against “price of the server”. It’s the total cost of ownership (TCO) over three years, with everything in. And “everything” includes items that your own server hides and the cloud charges you in plain sight.

With your own server, on top of the hardware price add what almost nobody notes down:

• Electricity and cooling running 24/7 for three years, not just the day you plug it in.
• A UPS and its battery replacement, plus redundancy if the service is critical.
• Licences for the operating system, virtualisation and backups.
• The recovery plan: if the machine dies on a Friday, how many hours until you’re operating again, and how much does that spare hardware cost?
• The administration hours: patching, monitoring and maintenance, which are money even if they never show up on any invoice.

In the cloud the enemy is different: the variable bill. Services are signed up for in one click and nobody switches them off. Machines left running overnight and at weekends, orphaned disks from dead projects, snapshots piling up and —the classic that wrecks budgets— data egress traffic, charged per gigabyte and invisible until you’ve already paid it. A cloud with no cost governance is more expensive than your own server; a well-governed cloud, with reservations and automatic shutdown, usually wins hands down.

Your own server hides half the cost from you; the cloud shows you all of it, which is why it scares people. Compare TCO over three years or you’re comparing nothing at all.

The practical rule: if your workload is stable and predictable (an internal application that works from 8am to 6pm, always the same), your own hardware or a rented dedicated server comes out very competitive. If your workload is variable, seasonal or of uncertain growth, the elasticity of the cloud is worth every euro: you pay for the peaks only when they happen and you don’t buy capacity “just in case”.

Control, security and compliance

The star argument for your own server is “this way I keep control and my data at home”. It’s a half-truth. You have physical control, yes. You also have all the responsibility: if you don’t apply the patches, if the firewall is misconfigured or if nobody checks the backups, the problem is entirely yours. Control and security are not the same thing. Many breaches happen on companies’ own servers precisely because they “were at home” and nobody looked after them rigorously.

The cloud works on a shared responsibility model: Azure and AWS secure the physical infrastructure, the network and the hypervisor —with certifications and audits an SME could never afford— but you are still responsible for configuring permissions properly, encrypting the data, managing identities and not leaving a bucket open to the internet. The cloud doesn’t make you secure; it gives you better tools to be secure, if you know how to use them.

On compliance, two keys for Spain and the EU. First, data residency: both Azure and AWS have regions in Spain and in the EU, so you can require that your data never leaves the European area (important for GDPR). Second, if you’re going for ISO 27001 or you work in a regulated sector, leaning on an already-certified cloud provider saves you a huge part of the journey, although certifying your own processes remains your job. Your own server doesn’t prevent it, but it forces you to demonstrate every physical and logical control yourself.

When each option makes sense (and the hybrid model)

Let’s get down to concrete decisions. There’s no universal winner, there’s fit.

• Cloud (Azure or AWS) if you grow fast or unpredictably, if you work remotely and need access from anywhere, if your workload has peaks, or if you don’t want —and shouldn’t have— anyone looking after hardware. Also if you value being able to deploy a new environment in hours.
• Azure specifically if you’re already a Microsoft house: 365, Windows Server, Active Directory. Identity integration and hybrid licensing tip the balance.
• AWS if your project is technical, with in-house development, containers or heavy automation, and you want the broadest catalogue of services on the market.
• Your own server if your workload is stable and known, if you have very low-latency requirements against machinery or systems on the shop floor, or if by contract/regulation the data must be physically on your premises. Careful: it demands a genuine continuity plan.

And then there’s the answer that wins more often than people think: the hybrid one. It’s not indecision, it’s strategy. You keep on your own or dedicated server what is stable, sensitive or cheap to have at home —your internal ERP, a file store, the critical database— and you move to the cloud what needs elasticity or a global presence: the website, email, test environments, campaign peaks. Many SMEs end up here because it pays off with the best of each model without marrying either one. The cloud as the destination for your backups is, moreover, the most sensible hybrid there is: you keep the safety net outside the building.

How MagicBoxDesk decides it and builds it

We don’t start with “we recommend Azure” or “we recommend AWS”. We start with your real workload: which applications you use, how many users, what peaks you have, what the regulations demand of you and what the three-year TCO of each scenario really adds up to. With those sums on the table —the ones almost nobody does— the decision stops being a hunch and becomes a number. From there we design, build and —this is what makes the difference— we manage it: 24/7 monitoring, tested backups, security and cost governance so the cloud bill doesn’t spiral out of control. You can see the detail in our infrastructure and cloud services.

The advantage of outsourcing your IT with us is that we decide with an engineer’s judgement and no commission from any vendor: we’ll tell you “your own server” if that’s what suits you even though we sell cloud, and vice versa. We’re your complete IT department, serving the whole of Spain with remote and on-site support. Tell us what you have and where you’re headed and we’ll tell you the right option with numbers, not brochures. Request a no-obligation quote and let’s do the sum that really matters, together.

The choice between cloud or your own server is almost always made for the wrong reason: a gut feeling (“our data belongs in-house”), the shock of a bill, or the buzz of a demo. Then reality hits: either a monthly fee that quietly doubles, or a rack of iron that in three years is worth less than the debt it created. It isn’t the technology’s fault, it’s the fault of deciding without running the numbers.

We’re not here to tell you which provider is better. We’re going to give you something more useful: the framework to decide with real criteria, and the true three-year cost calculation, the one that separates an engineer’s choice from an expensive hunch. With that number on the table, the answer is no longer a matter of opinion.

The question is framed wrong

“Which is better, the cloud or your own server?” has no answer, just as “is it better to rent or buy a warehouse?” has none. It depends on what you’re going to put inside, for how long, whether it grows, and what happens the day it fails. The right question isn’t what is better in the abstract, but what suits your specific case: your workload, your forecast, your risk tolerance, and what the law requires of you.

The underlying mistake is treating this as a technical decision when it’s a business decision disguised as a technical one. The cloud turns an investment into flexible operating expense; your own server turns today’s money into an asset you depreciate and control. They’re two opposite financial models, and choosing “because that’s what everyone does” is how thousands of euros are lost without anyone raising a hand.

There’s no winning option in the abstract. There’s a right option for your workload, your growth, and your tolerance for managing iron. Everything else is a brochure.

The factors that really decide it

Forget price for a moment. Before you calculate anything, there are five variables that tip the balance; get them clear and the number almost writes itself.

What your workloads look like. A stable, predictable workload —an internal ERP running 8am to 6pm, always the same— is a perfect fit for your own hardware or a rented dedicated server: you know exactly what it needs and you don’t pay for idle capacity. A variable or seasonal workload —campaign spikes, irregular traffic, projects that appear and die— calls for the elasticity of the cloud: you pay for the peak only when it happens and you don’t buy a server “just in case” for Christmas.

Criticality. Ask yourself how much every hour of that system being down costs you. If the answer is “an awful lot,” you need high availability: redundancy and fast recovery, something expensive and complex to build in your office and that comes as standard in the cloud. If the system can sit idle for a few hours without drama, your own server loses that disadvantage.

Cost predictability. Your own server gives you a fixed bill, but forces you to get the investment right up front. The cloud gives you flexibility, but the bill breathes every month and, without governance, it breathes upward. If your cash flow needs firm numbers, that weighs heavily.

Compliance. GDPR, ISO 27001, a regulated sector: these define where your data can live and what you have to prove. Many believe “in-house” complies better by default, and it’s false: a serious cloud provider is already audited and certified to a level no SME can afford, while your own server forces you to prove every physical and logical control yourself. What you must always demand is data residency in the EU.

Connectivity. The cloud is only as good as your line. If your office has a mediocre connection or a single operator with no backup, an internet outage leaves you unable to work. And the reverse: if you have machinery or shop-floor systems that demand very low latency, keeping them physically close can be a requirement, not a whim.

The 3-year TCO almost nobody calculates properly

This is where everything is decided, and this is where almost everyone gets it wrong. The honest comparison is not “monthly cloud fee” against “price of the server.” It’s the total cost of ownership (TCO) over three years, with absolutely everything inside. Each model hides its costs in a different place: your own server conceals them, and the cloud shows you all of them at once (which is why it scares people more than it should).

With your own server, on top of the hardware price you have to add what almost nobody writes down:

• Electricity and cooling running 24/7 for three years, not just the day you plug it in.
• A UPS and its battery replacement, plus redundancy if the service is critical.
• Licenses for the operating system, virtualization and backups, which renew every year.
• The recovery plan: if the machine dies on a Friday, in how many hours are you operating again, and with what spare?
• The administration hours —patching, monitoring, maintenance— money even if it never shows up on any invoice.
• Obsolescence: at three or four years it’s time to renew, and that cycle has to be provisioned from day one.

In the cloud the enemy is the opposite: the variable bill nobody watches. Services are signed up with one click and nobody switches them off. Machines left on overnight and at weekends, orphaned disks from dead projects, snapshots that pile up and —the classic budget-buster— data egress traffic, charged by the gigabyte and invisible until you’ve already paid for it. A cloud with no cost governance is more expensive than your own server; a well-governed one, with reservations and automatic shutdown, wins almost every time.

The rule that comes out of the exercise is simple: put both full columns side by side over three years, with management hours and hidden costs included, and compare. Most of the time the result isn’t what people expected before they sat down to add it up. That’s the value of running the number: it disarms the hunch.

Hybrid: the most frequent answer

When you run the number properly, the answer is often neither “all in-house” nor “all out,” but each thing where it belongs. Hybrid isn’t indecision or a bodge: it’s the strategy that wins more often than people think, because it takes the best of each model without marrying either.

The pattern that works best in SMEs: you keep on your own or dedicated server what is stable, sensitive or cheap to hold in-house —the internal ERP, the critical database— and you move to the cloud what needs elasticity or global presence: the website, email, campaign spikes. And there’s one hybrid almost nobody should skip: using the cloud as the destination for your backups. Keeping your safety net outside the building is the cheapest way to survive a fire, a burglary or a ransomware attack that encrypts your entire office.

The only requirement of a hybrid is that someone truly governs it: knows what runs where, watches the spend on the cloud side, and proves the backups restore. Without that discipline, hybrid is the sum of the flaws of both, not of their virtues.

How we run the number for you at MagicBoxDesk

We don’t start by recommending anything. We start with your real workload: which applications you use, how many users, what peaks you have, how much an hour of downtime costs you, and what the regulations demand. With that data we build the three-year TCO of each scenario —cloud, your own server, and hybrid— with every hidden cost inside, and we show it to you in a table you can defend in front of whoever signs the cheque. The decision stops being an opinion and becomes a number. You’ll find it in our infrastructure and cloud services.

And we don’t stop at the advice: we execute the winning option and manage it. We design, migrate and keep the system alive with 24/7 monitoring, tested backups, security and cost governance so the cloud bill never runs away. We’re your complete IT department, with remote and on-site support across Spain, and we decide with an engineer’s judgement and no commission from any vendor: we’ll tell you “your own server” if that’s what suits you, even though we also sell cloud.

Tell us what you have today and where you’re heading, and we’ll tell you the right option with numbers, not brochures. Request a no-obligation quote and let’s do the sum that matters together.