Documentation VIP Go Migrating and Importing Content

Migrating and Importing Content

Overview #

When you are ready to migrate content onto VIP Go, we will need a SQL dump and a compressed archive of the uploads directory. We process imports in two parts:

  1. Media, also frequently referred to as “uploads.” This requires a compressed archive of the uploads directory (usually zip or compressed tarball). If possible, it’s best to exclude intermediate images, as they are unnecessary (on VIP Go, image sizes are generated on the fly) and can increase the migration time.
  2. SQL dump of the WordPress migration source, typically from a development or staging environment where the site is being built and QA’d.

We can start importing the media at any time. It’s best to supply the initial archive as soon as possible, to give ample time for troubleshooting. It’s easy to follow-up with delta imports as needed.

↑ Top ↑

Frequently asked questions #

Q: Are user accounts imported from SQL, or manually created?
They are created from SQL.

Q: Are there typically any data-cleaning scripts or processes that need to be run on the final SQL import?
Typically, the only cleanup we run is wp search-replace on the domain if necessary. Ideally, the imported SQL would be ready to go as-is to make the switch over as fast as possible, but we can run wp-cli scripts if absolutely necessary.

Q: How do delta imports work?
You will provide us with an updated SQL dump and archive including any new images, and we will re-import. By default, this will update any older posts that have been modified, and add all new posts. With a delta, we will flush the object cache, but we may not need to flush the page cache (as it will automatically expire in 30 minutes).

Q: Does the theme need to be complete before we run the migration?
No, we can process imports at any time during the launch process.

 

 

Documentation is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.