Books & Media Store: From Magento to BigCommerce

Our client is a religious nonprofit offering books, media, and educational resources through their online store. These materials help their team share faith-based teachings and support learning within their community.

The organisation wanted to reduce Magento’s maintenance demands without giving up room for customisation. BigCommerce offered a managed commerce platform with APIs and headless capabilities, giving their team flexibility to develop the shopping experience with less responsibility for the underlying infrastructure.

Having already completed their Full Migration with LitExtension, the client returned to us to bring their new store up to date before launch. Our Recent Data Migration service allowed them to transfer customers and orders added to Magento after the initial migration, without repeating the full transfer.

Following the Full Migration, the client needed to bring BigCommerce up to date before launch. They asked us to:

• Transfer new customers and orders created in Magento since the previous migration.
• Provide migration records so their team could verify which data had been transferred.
• Coordinate the final data updates around their go-live schedule.
• Continue post-migration assistance as launch preparations progressed.

Before the new records could be transferred, our migration connection to Magento encountered two separate server issues. An incomplete SSL certificate chain prevented the connection from being verified, even though our server’s IP address had already been approved for access. After that issue was resolved, an HTTP 403 Forbidden error blocked further requests. These interruptions required investigation across our migration team, the client’s technical team, and their hosting provider.

The launch schedule added another complication. The planned September launch was postponed toward mid-October, extending the period in which Magento continued collecting new customers and orders. Data transferred earlier could therefore become outdated again before launch. The revised schedule also went beyond the original complimentary support period, requiring additional coordination to keep migration assistance available.

Our first priority was restoring access to Magento. We shared connection requests and error logs with the client’s technical team and hosting provider, helping them trace the SSL issue to an incomplete certificate chain. They installed a certificate with the complete chain, then resolved the separate server-side restriction causing the 403 error.

Once access was restored, we completed the Recent Data Migration to bring newly created customers and orders into BigCommerce. A further migration followed, accompanied by a mapping file showing the relationship between source and destination records so their team could verify the transferred data.

When the launch was postponed, our support arrangements changed with it. We extended complimentary post-migration support by two weeks, giving their team more time to prepare and arrange further data updates. For any delay beyond that extension, we also outlined an extended support option so they could plan the next steps.