![\"SAP](\"https:\/\/northbaysolutions.com\/wp-content\/uploads\/2022\/02\/IBL-casestudy-img.jpg\" "\\"SAP")
<\/span><\/div><\/div><\/div>Meet Our Customer<\/strong><\/p>\n<\/div> International Brands Limited<\/a> (IBL) Group is a world-class conglomerate managing a diverse portfolio of companies across consumer retail, healthcare, pharmaceuticals, distribution and e-commerce. IBL Group was built with a vision to achieve unparalleled reach through an unmatched distribution infrastructure. Marquee brands on IBL Group\u2019s client list include J&J, Red Bull, Mars and Kellogg's.<\/p>\n<\/div><\/div><\/div><\/div><\/div> The Challenge<\/strong><\/p>\n<\/div> When IBL engaged NorthBay Solutions<\/a>, it was for a very specific reason: they were seeking a new partner to guide them on their mission-critical SAP data migration<\/a> journey.<\/p>\n IBL wanted to become more agile, achieve cost efficiencies and improve stakeholder management. Moreover, they had been experiencing increasingly frequent downtimes that had real financial consequences. Beyond the internal cost of these interruptions, the downtimes were causing delays in delivery that had the potential to threaten relationships with their customers and supply chain partners.<\/p>\n IBL was ready to move forward with cloud migration<\/a> and data migration initiatives using AWS, because The Implication <\/strong><\/p>\n<\/div> By not following best practices when it came to spinning down test environments when not in use, IBL was incurring unnecessary costs. And, the complexity was becoming unmanageable. This prompted IBL to reach out to AWS directly for help. AWS recommended NorthBay Solutions being the only AWS Premier Consulting Partner and Managed Service Provider<\/a> in Pakistan, along with its expertise in AWS security best practices<\/a> with more than 300 AWS certified employees focused on helping organizations drive measurable business impact.<\/p>\n<\/div> Vision<\/strong><\/p>\n<\/div> Ultimately, what IBL<\/a> wanted was simple. IBL wanted to leverage the agility, flexibility and power of the cloud to modernize applications and introduce new capabilities such as data analytics, and Internet of Things (IoT).<\/p>\n<\/div> Solution<\/strong><\/p>\n<\/div> Discovery<\/strong> Next, NorthBay developed a detailed plan to migrate groups of servers in waves. Timelines for migration testing, User Acceptance Testing (UAT), and final cutover were calculated by analyzing the available migration bandwidth and synchronization speed obtained during discovery phase tests.<\/p>\n Migration<\/strong> Due to compatibility issues at OS level, SAP production systems were migrated at the application and database level by using SAP recommended methodologies<\/a>. For the AWS architecture design and deployment, the multi-account strategy, Well-Architected Framework, and Security by Design (SbD) approach were implemented. Control Tower and multiple AWS security and monitoring services were used. Transit gateway and site-to-site VPNs played a vital role in connecting AWS accounts and client offices.<\/p>\n<\/div>
\nthey knew that AWS SAP<\/a> would deliver the high levels of performance and uptime that their business-critical data processing workloads required.<\/p>\n<\/div><\/div><\/div><\/div>
\nThe NorthBay Solutions<\/a> team began by working closely with IBL and experts at AWS to analyze the requirements and provide a detailed road map for migrating their critical workloads. This collaborative team inventoried all existing servers, applications, and network equipment and analyzed their detailed specifications and cloud compatibility. It also documented any risks, such as a single point of failure which could disrupt the migration activity.<\/p>\n
\nAmong the initial 17 applications identified for initial migration included the complete landscape of SAP ERP<\/a>, Microsoft Exchange, domain controllers and some middleware servers. Based upon the discovery, some applications were slated for \u201clift and shift\u201d to AWS, while others would require application-level migration. AWS Elastic Disaster Recovery (CloudEndure Disaster Recovery) was used for block-level migration. After that, detailed UAT and end-user testing were performed to ensure each functionality was working properly after migration to the cloud. The discovery session information was collected utilizing templates from the TOGAF & AWS Enterprise Development Kit (EDK), which is part of the AWS Enterprise Development Framework.<\/a><\/p>\n