This paper analyzes a cloud transition case study involving the City of Los Angeles and its effort to migrate key information systems from an on-premise environment to a cloud-based one. The paper explores the critical considerations that arise when integrating legacy infrastructure with cloud services, including feature compatibility, data migration planning, and security. It further examines specific security measures the city negotiated with its cloud provider and proposes a phased, performance-based migration strategy as a best practice model for similar large-scale public-sector cloud transitions.
Based on the Cloud Transition Case Study involving the City of Los Angeles and its attempt to reconfigure the architecture of some of its most integral information systems from an on-premise environment to a cloud-based one, there are a number of important considerations when integrating components with legacy infrastructure. Many of these pertain to the features and capabilities — and the differences between them — in the two models. For instance, after agreeing to implement the cloud as a replacement for the city's on-premise calendaring and electronic mail system, the city discovered that several features playing an integral role in the operations of the former system were simply not supported by the cloud version.
Thus, it is necessary to list the most widely used and vital characteristics of one's current system to determine how they align with those of the new system. It may be possible to modify aspects of the latter to accommodate the capabilities relied upon in the former. Regardless, it is essential to compile a list of specific use cases and the features required for each, and to present these to the cloud service provider — ideally before agreeing to implementation — to ensure that it can accommodate all of an organization's needs.
Another critical consideration involves the actual transition from the legacy system to the cloud. Many of these concerns pertain to the migration or replication of data from the on-premise environment to the virtualized one that cloud computing offers (Williams, 2012). In practice, a significant number of these measures involve general organization and sanitization of data used in an organization's existing architecture. For instance, the City of Los Angeles had to undertake several administrative efforts to ensure its email system would be properly migrated to the cloud, including deleting certain emails, stratifying mail by year, and saving emails in a particular format so they could be readily archived and accessed via the new system.
These concerns are closely tied to the specific capabilities of the new email system, which simply reinforces the necessity of determining what capabilities a new system offers and how they can accommodate the particular needs of an organization and its use cases.
Perhaps the most significant concern when integrating legacy infrastructure with a cloud environment relates to security. Security has long been one of the most pervasive issues in cloud computing, particularly regarding the hosting of sensitive, proprietary data outside of an organization's own firewalls (Harper, 2014). Not all security-related considerations are direct, however. For instance, due to inadequate security measures in the new cloud environment, the City of Los Angeles was forced to migrate some of its data — which had already been successfully relocated to the cloud — back to its physical environment. This proved both time-consuming and costly.
It is therefore essential to determine how well a new system can account for all of the needs of a legacy system, including those not necessarily related to features or capabilities but pertaining to vital security measures. Ideally, the degree of security and the specific measures to be employed should be established prior to migrating any data from legacy systems. A prolonged migration process in which data is replicated to the cloud only to be replicated back to legacy systems — particularly for security reasons — should be avoided at all costs.
This case study provided a great deal of insight regarding data migration and the transition from legacy systems to more modern ones. It also substantially broadened understanding of the privacy, security, and data management strategies the City of Los Angeles attempted to implement. As previously noted, security concerns have long served as the proverbial caveat for managing data in the cloud. Mechanisms such as encryption, masking, and tokenization (the use of security tokens) are fairly standard in contemporary practice and demonstrate that cloud service providers have come a long way in addressing this fundamental need (Harper, 2014). When these measures are combined with hybrid cloud options — including solutions that integrate both public and private clouds — many organizational security concerns can be effectively addressed. However, given the large volume of sensitive personal information involved, including criminal records, social security numbers, and data valuable to police and fire department operations, the depth of security considerations in this case study is not surprising.
"Unique contractual security provisions negotiated by the city"
"Tiered payment and departmental migration recommendations"
The City of Los Angeles case study illustrates that a successful cloud migration depends not only on technical compatibility but also on contractual discipline and a phased, performance-verified approach to deployment. Organizations transitioning from legacy systems must assess feature alignment, plan for data sanitization, and negotiate robust security provisions before any migration begins. A tiered payment structure and incremental departmental rollout would have mitigated many of the cost overruns and security shortfalls experienced in this case, offering a replicable model for future public-sector cloud transitions.
You’re 55% through this paper. Sign up to read the remaining 2 sections.
Sign Up Now — Instant Access Already a member? Log inAlways verify citation format against your institution’s current style guide requirements.