Which Workloads Should Stay On-Prem, and Which Should Go to the Cloud? Six Concrete Examples

The right question is not "cloud or on-prem" but "which workload lives where". This article is that framework's application — the abstract criteria applied to six concrete SMB workloads, with the verdict and its reasoning written out for each. Lay your own estate over these six examples and your migration plan's skeleton falls out.

The Five Decision Criteria

Criterion	Its question	Favours on-prem	Favours cloud
Latency	Do milliseconds affect the user?	If yes	If no
Data weight	How heavy is the daily working data?	Heavy	Light
Load pattern	Steady or spiky?	Steady 24/7	Spiky/seasonal
Residency/compliance	Does where the data sits matter legally or contractually?	Strict requirements	Flexibility
Maintenance capacity	Who will keep this system alive?	Strong IT support	Limited capacity

Example 1: the Accounting/ERP Server → On-Prem

The classic SMB ERP points on-prem on three criteria at once: users are latency-sensitive (every entry screen round-trips to the server), the load is steady 24/7 (in the cloud, rent runs every hour) and the software's licensing/version model is usually designed for local installation. The right modernisation is not forcing it to the cloud but virtualising it on-prem and backing it up properly; when the vendor's own cloud edition matures, the decision is revisited.

Example 2: Email → Cloud

Email's character is the cloud's textbook case: access-from-anywhere is the natural need, latency tolerance is high, and the maintenance load (patching, the spam war, disk growth) is heavy when kept on-prem. An on-premises mail server now needs a specific justification; the default answer is the cloud suites.

Example 3: the File Server → Hybrid

Files belong to both worlds: heavy in-office work wants local speed (the NAS); sharing and remote access want the cloud. So the decision splits: the working copy inside, the sharing layer outside, and every folder family's single home decided. Hybrid's one sin bears repeating: the same folder cannot live as two "current" copies in two worlds.

Example 4: Backup → Crosswise

Backup owns the most elegant answer to "on-prem or cloud": both, crosswise. On-prem systems back up both to a local repository (fast restore) and to cloud/off-site (disaster protection); cloud data (email, files) also gets a copy independent of its provider. Being in the cloud is not being backed up — the sentence most often forgotten after a migration.

Example 5: the Website and External Services → Outside

The corporate site, externally facing applications and customer portals belong not at the end of the office's internet line but in hosting environments designed for the job: uptime, scale and attack-surface management are professional there. A website hosted at the office needlessly shoulders the static-IP, port-forwarding and line-redundancy chain — the exception is a specific compliance rationale.

Example 6: Camera Recording → On-Prem

Streaming continuous camera footage to the cloud is the quiet enemy of bandwidth and the cloud bill: dozens of cameras' 24/7 video strains a typical SMB line and budget. The standard pattern is local recording (NVR) + only event clips/critical-angle backups to the cloud. The remote-viewing need is solved with secure access, not by moving the recording.

The Anti-Pattern: the Half Migration

The costliest state is indecision: the ERP on-prem but its reporting copied to the cloud, half the files on the NAS and half across three clouds, the email migration "trial" running on two systems for months. A half migration pays both worlds' costs and enjoys neither's comfort. The medicine is the workload map: every system's name, current home, decided home and migration date in one table — until no system remains undecided.

The Workload Map with Yamanlar Bilişim

Our hybrid assessments produce exactly that table: every workload in your inventory run through the five criteria, a verdict and rationale written on each row, migrations sequenced with outage windows and the budget calendar. The decision meeting runs on that single page, not on jargon — management knows what it approved and why.

FAQ