A path for moving to AWS: trajectory framing, a landing foundation, a pilot, then waves. A full re-architecture remains the High-Speed sprint.
Royalty-free image — Unsplash
Migration framing and plan
Domain
Migration
Description
An inventory of the data centre from material supplied by the client. A trajectory per application (relocate, rehost, replatform, refactor, repurchase, retire, retain), target architecture, wave order, risks, and an order of magnitude for AWS cost. Deliverable: a migration plan ready to execute.
Assumptions and conditions
Delivered 100% remotely by a principal cloud architect.
Orwin Cloud is used for diagnosis and to check the remediation. This use is not billed during the engagement.
Code assistants (Kiro, Cursor, GitHub Copilot) are used under ITechSource secure conventions. This use is included.
Prices exclude tax. Engagement packages follow a rate of €1,200 per day. Training is sold per session.
Reference baseline: one SME or one application, in a single organisation. Adjustable on request, at the same rate.
Out of package: AWS consumption, penetration testing, on-call, and an Orwin Cloud subscription kept after the engagement.
Reference baseline, adjustable on request: up to 15 applications or 40 machines.
