IBM Classic Site to Modern Site Migration for First Quality

It offers consumer paper products, bottled water, engineered fabrics, tampons, baby wipes, wet wipes, paper towels and bath tissues, baby diapers, sanitary pads, baby pants, and sleep overs.

Business Challenge

• The Client has their Sitecore applications deployed in Azure which were accessed by Internal and External users.
• SAML based authentication is implemented for external and internal users to access the Sitecore applications and LDAP based authentication is implemented for internal users to access the .Net Applications
• The Biggest challenge the client faced was that there was no single identity access management application for handling authentication for internal and external users
• They were also using a content delivery tool called WordPress through which the Sales leads (external users) were accessing the content of the Sitecore applications.
• The client also wanted to restrict the content access for External users for the Sitecore applications.

How Avasoft helped?

• Just for this reason, we didn’t want our client to go back to an older version which would sooner be replaced when Microsoft released updated features for Modern sites.
• To address this scenario, we made some architectural changes to our AVAMIGRATRON (migration) tool with which we figured out features similar to Classic sites in the Modern view. Since Modern view did not support hierarchical structure, we followed site to site and sub-site to site migration technique.
• Let’s take, for example, Classic sites have blog templates but Modern site did not have it then. So we migrated all the blog content to Modern site pages (sub-site to site).
• Even before Microsoft released many of the features in the Modern view then, we re-architected our migration tool, AVAMIGRATRON to accustom all the features as in the Classic sites