Finance / Asset management
CI Financial: Automating server migration input validation, staged execution, approvals and reporting
- Company
- CI Financial
- Country
- Canada
- Adoption stage
- In operation
- Source published
- Date basis
- The date the source was published. It can differ from the date adoption started.
- How the source was checked
- Read the full source text
The work problem
CI Financial needed to migrate servers supporting trading, batch processing and other workloads to AWS before its VMware renewal deadline. Complex server-to-application relationships and stale hostnames or incorrect addresses could propagate errors into migration jobs. Teams across regions also needed to avoid collisions and service interruption.
Technology and data
CI Financial and AWS Professional Services created separate wave jobs within a shared AWS Transform workspace. An external intake pipeline validated authoritative server and application data before submission; shared prompts supported readiness and execution checks. Contributors ran jobs, approvers reviewed operational gates such as test launches, and read-only stakeholders monitored progress. Kiro consolidated AWS Transform status data into reports.
Results
The joint AWS and CI Financial article reports migrating 215 application servers and 44 database servers in 23 weeks with zero infrastructure rollbacks across all waves. Average time from starting a server launch to running in AWS was 22 minutes. A validated intake file and reusable prompt made a wave launch-ready in under 10 minutes.
Limits and open questions
The 22-minute average excludes planning, testing and post-launch work. The former two-to-three-hour preparation effort and readiness-check savings are estimates in the article, not measured total cost savings.
Sources
- How CI Financial ran parallel teams on AWS TransformAWS / CI Financial, Accessed
Compiled from public sources. These are not results from ATF Works customers.