The Ministry's Cloud Accounting Migration
A ministry plans to move its accounting system to a cloud platform. The current system is 12 years old, runs on a local server, and produces monthly reports three weeks after month-end. The new system costs Tk 45 million over five years, plus Tk 6 million annually for training. The vendor promises real-time reporting and a 40% reduction in processing time. Internal audit finds that 30% of staff lack basic spreadsheet skills, and the ministry has no data-protection policy. The national data centre requires government data to reside domestically, but the vendor's primary servers are abroad. The ministry's budget cycle requires a procurement plan approved by the finance division before commitment.
1. Assess the risks of the migration and recommend whether to proceed, defer, or proceed with conditions.
Read the worked answer
Benefits are plausible but unproven. A three-week reporting lag is a genuine problem, and real-time data would improve budget monitoring. However, the 40% processing-time claim is vendor-supplied and should be validated against a pilot.
Key risks.
- Data sovereignty. Foreign-hosted servers conflict with the domestic-residency rule. This is a legal blocker, not a preference.
- Skills gap. With 30% of staff lacking basic skills, training of Tk 6 million per year may be insufficient, and productivity may fall before it rises.
- Data protection. No policy means personal and financial data could be mishandled; this also creates legal exposure.
- Procurement compliance. Committing before finance-division approval would breach the budget cycle.
- Vendor lock-in and exit. Five-year contracts without data-portability clauses create dependency.
Recommendation: proceed with conditions, not unconditionally. Conditions should include: domestic hosting or a certified local data centre; an approved data-protection policy before go-live; a phased rollout starting with one division; a validated pilot; contractual data-portability and exit clauses; and finance-division approval of the procurement plan before any commitment. Deferral is the fallback if domestic hosting cannot be secured.
2. Design a phased implementation plan with measurable milestones.
Read the worked answer
Phase 0 - Readiness (months 1–3). Approve the procurement plan; adopt a data-protection policy; secure a domestic hosting arrangement; complete a skills audit. Milestone: signed hosting agreement and approved policy.
Phase 1 - Pilot (months 4–8). Migrate one division's transactions in parallel with the legacy system. Deliver basic training to all pilot staff. Milestone: pilot reports produced within five days of month-end, with reconciled balances against the legacy system.
Phase 2 - Rollout (months 9–15). Extend to remaining divisions in two waves. Run parallel processing for two months per wave. Milestone: 90% of staff certified in basic use; month-end close within seven days.
Phase 3 - Optimisation (months 16–24). Retire the legacy system; introduce real-time dashboards; conduct a post-implementation review. Milestone: independent audit confirms data integrity and control effectiveness.
Governance. A steering committee chaired by the accounting officer, with finance, audit, and IT representation, meets monthly. A risk register is reviewed at each meeting.
Metrics. Reporting lag, reconciliation exceptions, training completion, system uptime, and cost against budget. A stop-go gate after Phase 1 prevents sunk-cost escalation if the pilot fails.