Damco

Move the applications that gain from the cloud We place each one by what it costs now and what it'll cost there

Start with the shape of each application's load The customer portal idles every night, and idle servers still send a bill

Then price each way to move it, month by month Servers sized for the peak cost the same at midnight as at noon

The customer portal is quiet every night and weekend, so it's replatformed in wave 2, not lifted and shifted.

Land it in your account, under your rules Your directory signs people in, and your security team sees every log

Microsoft Rails, for moves to Azure
  • It runs in your accountWe work inside your cloud account, and you can see everything we do there.
  • Your directory signs everyone inOur engineers sign in the way your people do, and lose access when the work ends.
  • Every change has an authorChanges go through code and review, so each one has a name and a reason.
  • We leave what runs better where it isIf an application gains nothing from the move, we tell you and it stays.

Then run it until the cost per order falls The customer portal's cost per order is on our monthly report, beside each change

Customer portalCost per orderMay to October
1234
Releases this month6Open incidents0Reviewed withYour IT lead
What we changed, newest first
  1. 4OctoberTurned off three test environments nobody has used since June.
  2. 3SeptemberCommitted to a year of the steady database, at a lower rate.
  3. 2JulyMoved logs older than 90 days to cheaper storage.
  4. 1MayScaled the order service down from 8 pm to 6 am.

Tell us which applications you'd move first

We'll place each one in five days, with what it costs today and what it would cost in the cloud. You keep the plan either way.