A company that makes brakes has a fairly clear idea of what failure looks like. For Performance Friction Corporation, however, the trouble described in its cloud migration story was inside the business: aging infrastructure, crashing software, custom code and a small team facing a large assignment. The manufacturer needed a digital overhaul. Someone still had to connect the software to the shop floor.
That assignment helps explain Velocity Technology. The Charlotte business worked in the space between an application running somewhere and an application doing its job. Payroll, inventory and financial reporting made the distinction consequential. Velocity supplied the people and management tools to carry those systems into cloud environments and look after them there.
- Its specialty was business-critical applications: SAP, Oracle, Infor and their surrounding systems.
- Customers bought migration, ongoing management and application expertise.
- Navisite acquired Velocity in 2021. Accenture acquired Navisite in 2024.
A brake maker, a software problem
Performance Friction makes brakes for motorsports, vehicle manufacturers and first responders. Its case, published on the AWS blog in 2020 by a Velocity executive, describes an implementation of SAP S/4HANA connected to shop-floor systems. The resulting environment supported forecasting and financial reporting. A functioning factory and useful financial numbers belonged in the same conversation.
This was Velocity’s market: organizations with substantial software estates and limited appetite for disruption. Its portfolio combined cloud infrastructure, database management, disaster recovery and functional consulting. Its proprietary Velocity Cloud Application Management Platform, or VCAMP, provided application management and visibility. The infrastructure and the application specialists came together in a managed service.
The distinction matters when comparing providers. A company can rent computing capacity, retain its own application team or hire an ERP consultancy. Velocity’s proposition bundled work across those boundaries. For a buyer, the useful question was how much responsibility the provider could actually take for the application and its business processes.
The commercial logic followed the application’s life. A migration or implementation created project work; keeping the environment available created an ongoing management relationship. Customers could buy specialist help without assembling every required skill internally. The value depended on the complexity of the estate and the work the customer could hand over.
The purchase order is the point
Consider a less glamorous customer problem. Knape & Vogt, the hardware and storage-products manufacturer, needed its Oracle E-Business Suite to agree with legacy logistics data after acquiring SaddleCreek. Its import process required frequent human intervention. Transactions failed; people repaired them. The warehouse could move goods while the software needed help recording what had happened.
Velocity changed the receiving-data process. Its team restructured a staging table, created a table to archive duplicate records and added validation rules. The work covered ordinary purchase-order receipts and transfers between organizations. According to the case study, failed transactions fell and manual intervention was virtually eliminated.
- 01Receipt data enters
the staging table - 02Validation catches
problem records - 03Oracle records
the transaction
That is a concrete answer to what customers could do with Velocity. They could bring an application problem to people who understood both the software and the process it represented. The immediate benefit in this case was fewer exceptions to repair. The repair was specific enough to inspect: tables, duplicates, validation.
Buying people who knew the applications
Velocity expanded that expertise through acquisitions. A Silver Lake Sumeru-led investor group and management acquired the company in 2012. The following year, buying Glasgow-based velos-IT extended its European presence and Oracle E-Business Suite capabilities. Geography and application knowledge grew together.
The larger move came in April 2014: approximately $80 million for Titan Technology Partners. The transaction added SAP and PeopleSoft capabilities and strengthened existing Oracle and Infor services. The combined business reported more than 750 employees and approximately $150 million in revenue. Those figures describe the company after that deal.
“Cloud is evolving beyond infrastructure hosting and towards a full spectrum of business management solutions.”
Tom Bruno, then CEO, April 2014
Buying Titan made Bruno’s argument tangible. Velocity was assembling expertise in how customers used their applications. In 2017, it acquired Oracle specialist Mercury Technology Group. Its public cloud credentials developed too: by September 2019, Velocity had attained AWS Premier Consulting Partner status.
185 systems. One business to keep running.
Change Healthcare supplied a different test. After acquiring a business segment in late 2017, it needed to consolidate data centers and integrate enterprise workloads. SAP and Oracle systems had to move while the technologies of two businesses were connected. Migration and integration were parts of the same assignment.
SAP and Oracle migration for Change Healthcare, documented by AWS in 2020.
AWS reported that Velocity led the migration of 185 systems within 12 months. The account also described turnaround times falling from weeks to minutes. That result belongs to a particular customer and project. It gives a buyer something useful to investigate: which activities became faster, and what work made that possible?
The business moved on. The lesson travels.
Navisite acquired Velocity Technology Solutions in January 2021. Accenture completed its acquisition of Navisite in January 2024. The old velocity.cc address now carries articles about cloud computing and data rooms. Velocity had already announced a move to the VelocityCloud.com domain in 2015. The historical managed-services business is the subject here.
The practical lesson is to begin a cloud conversation with a named workflow. Count failed imports. Identify who repairs them. Ask what happens to an order when a record is rejected. Then judge the proposed service against that work. Capacity, monitoring and application knowledge need to meet at a measurable business outcome.
A useful buying exercise follows from those examples: put a technical operator and a business process owner in the same review. Have them agree on what a successful receipt, report or recovery looks like. Then test the service against that definition. A migration date is a milestone; a transaction that completes reliably is a result.
This approach suits complicated, inherited application estates. A small company using a few browser-based tools may have little need for such an arrangement. Moving an application also leaves its data rules and business decisions to be addressed. Velocity’s most instructive work shows where to look: the ordinary transaction that keeps asking a human to rescue it.