The way our process works is we perform a final sync of your website just prior to cutover, so we’ll bring your Pagely instance current with any code/content changes that have occurred following the initial migration. We do that just before you cutover DNS, so your Pagely instance will be identical to your existing/production instance at cutover time. You would need to do a content freeze just before we do the sync and before DNS cutover, and we will coordinate this with you.

Using PressDNS™ yields special benefits to our customers, folding in Amazon Route53 service and our PressCACHE™ tools to enhance the processing time of your web requests and WordPress page rendering speeds. Find more details on how to effectively use PressDNS™ in the linked Support Knowledge Base article.