The first migration did not finish the job
The firm had grown to more than 1,100 employees across 12 locations. After its original on-premises system approached capacity and end of life, the first cloud service still produced dropped calls and company-wide outages lasting at least four hours once or twice a year.
That history makes the case more useful than a straightforward claim that cloud service improves reliability. The delivery model had already changed, yet the practical failure remained: clients could not consistently reach staff. The relevant comparison was between operating experiences, including how the service behaved during normal administration, rather than between the labels attached to the two architectures.
Administration was part of the reliability problem
The first provider’s administration portal also experienced downtime and required workarounds to make configuration changes persist. After at least a year researching alternatives, the firm selected RingCentral.
This matters because the management interface is part of a communications service’s operating surface. Staff moves, routing changes and new locations depend on it even when existing calls appear healthy. A difficult or unavailable portal can leave a technically connected system misaligned with the organization it serves. The firm’s experience connected user-facing call problems with the IT team’s ability to maintain the service.
Business numbers became usable away from the desk
RingCentral’s mobile application and softphone let attorneys use business numbers away from their offices without sharing personal mobile numbers. Call records and transcriptions also helped staff locate case details and compile billable time.
The change therefore extended beyond replacing a dial tone. The business identity used for a call no longer depended on a lawyer being beside a particular desk phone. At the same time, the surrounding call information became useful after the conversation ended. Those are distinct operational benefits: reachability concerns whether the conversation happens, while usable records concern what staff can do with it afterward.
The outcome was reported experience, not a universal uptime promise
The firm’s CIO reported no outages after the RingCentral rollout. The account did not specify the length of that observation period. Larger continuing-education webinars were a planned extension, not part of the completed outcome.
Cartennas’s assessment is that the second migration succeeded by addressing the shortcomings left by the first. The important result was a more dependable and manageable way for a distributed firm to communicate, with mobility tied to business identity. The case also establishes a useful limit: choosing a cloud platform is an architectural decision; reliable calls, workable administration and useful records are operating results that still have to follow.