Moving to the Cloud Does Not Fix a Bad IT Environment Automatically

Cloud use is already routine in legal practice. The ABA's 2024 Cloud Computing TechReport found that about 75% of surveyed attorneys were using cloud computing for work-related tasks. The reasons are familiar: people want access away from the office, reliable availability and better backup options. At the same time, security and confidentiality remained the leading concerns among respondents.

For a law firm that still depends on aging servers or an awkward remote-access setup, moving infrastructure to Microsoft Azure can make sense. What sometimes gets lost in the planning is that Azure receives the environment the law firm gives it. If that environment contains old applications, unnecessary user access, oversized servers, duplicate files or workflows that have annoyed staff for years, a migration alone will not sort them out.

A 15-year-old accounting application running from an Azure virtual machine is still a 15-year-old application. A folder that everyone could access before migration can remain broadly accessible afterwards. 50 GB of duplicate matter files are still 50 GB of duplicate matter files once they reach cloud storage.

The First Migration Decision Is What Deserves to Move

One of the easiest ways to make a cloud project unnecessarily expensive is to assume that everything currently running on-premises should be recreated in Azure.

A law firm might discover an old server supporting software that only two people use. Another server may have been kept alive because nobody is certain what will happen if it is switched off. There could be a database connected to a case-management system through an integration configured by a vendor years ago. Staff may know that a particular scanner or accounting application "needs the server," while nobody has documented exactly why.

Those details matter before anything moves.

Microsoft's Cloud Adoption Framework separates migration planning from the migration itself for this reason. Its current workload-assessment guidance recommends documenting architecture, application components, databases, security requirements and both internal and external dependencies before choosing a migration approach.

Microsoft also distinguishes between several migration strategies. A workload can be rehosted with relatively little change, replatformed, refactored, replaced, rebuilt, retained where it is or retired altogether. There is little value in paying to migrate an application that the law firm no longer needs.

That sounds obvious on paper. Inside a long-running law firm environment, finding those systems can take some digging.

Legal Software Brings Its History With It

Older legal applications are often the awkward part of the project. A law firm may have used the same billing, document-management or practice-management product for years. Lawyers and staff know how it behaves. The database contains important historical information. Replacing it during an infrastructure migration may introduce more disruption than the law firm is willing to accept.

Keeping the application can be reasonable. The question is whether it will work properly in the environment being planned. Some older applications depend on a particular version of Windows Server or SQL Server. Others expect a mapped network drive. There may be licensing restrictions, local hardware dependencies, service accounts or integrations with another application that nobody sees during normal use.

Microsoft recommends identifying unsupported and deprecated components during the assessment stage and documenting remediation that may be required before migration. Its guidance also calls for third-party software compatibility and licensing requirements to be checked when planning the target Azure environment.

Sometimes the answer will be to move an application largely as it is and deal with modernization later. At least then the law firm knows what it is carrying forward.

Old Permissions Are Easy to Preserve by Accident

Access tends to grow over time. A paralegal joins a large litigation matter and gets access to the relevant folder. Six months later, the matter ends but the permission stays. An attorney transfers between practice groups. A consultant receives temporary access. Someone asks IT to give a new employee "the same access as Sarah" because that is quicker than working out exactly what the employee needs.

After several years, the original reasoning behind some of those permissions is gone. Cloud migration gives a law firm a chance to review that history. Simply reproducing the same groups and privileges in the new environment misses that opportunity.

The CISA Cloud Security Technical Reference Architecture recommends least-privilege access in cloud environments and specifically discusses auditing for over-privileged accounts and other access misconfigurations. Microsoft follows the same principle in its Azure guidance, recommending that access be granted at the lowest practical scope required for a user's responsibilities.

For a law firm, the exercise can be quite practical. Who still needs access to this client? Which users require administrative rights? Who owns each security group? What access disappears when somebody leaves the law firm? Are former practice-group memberships still hanging around?

Those questions existed before the migration. Azure simply gives the law firm a good reason to answer them.

A Messy File Server Does Not Become an Organized Document System

File migrations create a similar problem.

Imagine a shared drive with folders called "CLIENTS," "Old Clients," "Closed," "Archive 2020," "John's Matters" and "Move Later." Inside those folders are duplicate PDFs, working drafts, scanned documents and years of material nobody wants to delete because nobody is sure whether it can be deleted.

Copying the entire structure into a new cloud environment preserves the problem with a new address.

This matters beyond neatness. Search, document automation and newer AI tools become far more useful when documents have sensible locations, predictable permissions and clear ownership. Poorly organized information makes all three harder.

Nobody needs to turn a cloud migration into a six-month exercise in renaming every file. There are usually obvious categories worth addressing first: active and closed matters, administrative records, personal working files, duplicated data and folders with unusually broad access.

The ABA's cloud research gives some context for why law firms should pay attention to this part of the project. In its 2024 survey, confidentiality and security were cited as cloud concerns by roughly 55% of respondents, while concerns about control of data were reported by about 38%. Yet only 48% said their law firms had changed internal policies in response to cloud adoption. Technology can change much faster than the habits around it.

The Cloud Cannot Fix a Workflow Nobody Has Changed

There is another category of problem that no server migration will solve. A new client sends information by email. An assistant copies it into a practice-management system. Someone else creates a folder. The same information gets entered into billing software. A lawyer later asks for a spreadsheet because the reporting available from those systems is not what they need.

All of this can continue perfectly well after a move to Azure. The cloud may make the applications more reliable or easier to reach from home. Staff are still entering the same information three times.

These are the kinds of details worth collecting during migration interviews. Attorneys may complain about speed, while their assistants know that the larger problem is the number of manual steps. Accounting may have a workaround that IT has never seen. An application everyone describes as "essential" may turn out to be used once each month because another system never got configured properly. A migration does not require fixing every process. It does help to know which problems belong to infrastructure and which belong to the way the law firm works.

Moving an Oversized Server Can Also Move an Oversized Bill

Cloud pricing makes another old problem easier to see. An on-premises server was often purchased with enough capacity to cover several years of anticipated growth. Once the hardware was bought, nobody received a separate monthly bill showing how much unused CPU or memory was sitting there.

Azure works differently. Azure Migrate can collect performance information from existing workloads and make right-sizing recommendations based on CPU, memory, storage and network requirements. Microsoft's assessment tools can also estimate the monthly cost of running the proposed workload in Azure.

That matters because copying the existing server specification directly into Azure may mean paying every month for capacity the law firm rarely uses. Microsoft's Well-Architected Framework recommends reviewing underused resources, eliminating obsolete components and adjusting resource sizes as workload requirements become clearer. Cost optimization is easier when it begins before migration instead of after several surprisingly large invoices.

Smaller Migration Waves Can Reveal Problems Before They Spread

There is rarely much benefit in moving an entire environment at once simply for the sake of finishing quickly. Microsoft's current migration guidance recommends grouping related workloads into waves and using lessons from earlier migrations to improve later ones. Dependencies matter here. A document application and its database may need to move together. Another system may tolerate running in a hybrid environment for a period.

For a law firm, a smaller first wave also gives the IT team time to see what users experience after the move. Do documents open as expected? Is printing normal? Does the legacy application still communicate with the database? Are remote users seeing delays? Did permissions carry across correctly? Is the new backup process working?

The answers are much easier to deal with when twenty users have moved than when the entire law firm has.

A Better Cloud Project Leaves Some Old Baggage Behind

There will almost always be compromises. A legacy application may have to stay. Some old data may need to remain available for retention reasons. A workflow that deserves redesign may have to wait until another project. The useful distinction is whether those decisions were made consciously.

A law firm should know that an application is being carried forward because replacing it would create too much disruption. It should know why a particular group has broad access. It should know why historical data is being retained and what an old server still does.

Without that work, the law firm can finish a technically successful migration and still hear the same complaints six months later.

AKAVEIL TECHNOLOGIES works specifically with law firms on the systems surrounding these decisions, including cloud infrastructure, Microsoft 365 Copilot and cybersecurity. That can include assessing the existing environment, understanding application and data dependencies, reviewing access, planning an Azure migration and dealing with the older technology that law firms often cannot replace overnight.

If your law firm is considering a cloud migration, or has already moved and suspects that some of the old problems came along with it, contact AKAVEIL or write to info@akaveil.com.

About Ariel Perez

Ariel Perez is the Founder and CEO of AKAVEIL TECHNOLOGIES and has spent nearly two decades working in IT, cloud infrastructure and cybersecurity. He works closely with law firms on cloud migrations, Microsoft Azure, Microsoft 365 and the older applications and infrastructure that often have to be accounted for during modernization projects.

Much of Ariel's work involves helping firms understand what should move to the cloud, what should be cleaned up first and which legacy systems or dependencies need to be handled carefully so that existing IT problems are not simply carried into a new environment.

For questions about cloud migration, Microsoft Azure or modernizing your law firm's IT environment, contact Ariel at info@akaveil.com.