JDA Software is the leading provider of end-to-end, integrated retail, omni-channel and supply chain planning and execution solutions. Serving more than 4,000 customers worldwide, JDA’s unique solutions empower their clients to reduce costs, increase profitability and improve collaboration. As a result they can deliver on their customer promises every time.
An established global leader in supply chain and logistics, JDA Software requires a rock-solid IT infrastructure. They must track and manage commodities as they move from raw materials in the manufacturing process all the way to the finished product on storefront shelves for instance. After going “All in on the Cloud,” JDA’s IT department moved all of its central applications off-site, into the cloud, and is now using an SAS-model for all of its integrated supply chain management and logistics products.
The Challenge: On-Prem to OneDrive Migration On A Deadline
After moving its customer-facing IT applications into the cloud, JDA Software needed a way to migrate its global user base from on-premises network file shares to cloud-based storage.
“Our existing on-premises file storage architecture was becoming burdensome. We were doubling our amount of SAN storage every three years,” said Mark Fling, Vice President of Infrastructure and Operations at JDA Software. “That gets to be very expensive, very quickly. With cloud storage, we can be much more flexible in terms of how we deliver IT services worldwide and we have the ability to scale up and down based on business requirements. It’s a win-win situation.”
After already implementing two cloud storage providers, JDA Software decided to consolidate its user base to one single platform. They planned on using Microsoft’s Office 365 with OneDrive. However, IT had a tight deadline of 60 days to move 1,400 users from its existing cloud storage services into the Microsoft Environment.
To complete the OneDrive migration, JDA chose a popular SharePoint and Office 365 migration tool to move their users and content. However, it was quickly discovered that the tool was inadequate.
“We found that there were several major failures in terms of throughput. There was a very tight deadline of migrating 700 gigabytes per week, and the tool simply could not deliver that,” Fling said. “We tried for several weeks, but it became apparent very quickly that we weren’t going to make our deadlines.”
After struggling with their initial migration tool, Fling said JDA asked their consultants at Statera to seek out a different, more effective product.