Internal RWP Documentation

⌘K
  1. Home
  2. /
  3. Docs
  4. /
  5. Internal RWP Documentatio...
  6. /
  7. Articles
  8. /
  9. Migrating to Bluehost Clo...

Migrating to Bluehost Cloud via WP Migrate Pro

Push vs Pull

In general, either will work when going between 2 publicly available domains (i.e. domain website & temp URL site). However, there are a few differences between Push/Pull that might affect which option is best. Here are some I found:

  1. Wordfence Security plugin‘s firewall might cause issues w/ Push & require disabling it or doing a Pull instead
  2. Local environments & other non-publicly accessible URLs require initiating a PUSH or PULL on Local, so migration can access the publicly available URL on the other end. See plugin documentation for more details.

Database

Checked & leave default settings, typically.

Media Uploads

Checked & leave default of “PULL ALL MEDIA UPLOADS”.

Theme

Checked & select ” Pull only active themes
Note: if only active themes are present, then leaving default “Pull all themes” is equivalent.

Plugins

Some plugins that cause the migration to fail:

  1. Select “Pull only selected plugins
  2. Check only active plugins, do not migrate inactive plugins
  3. Uncheck any of the following plugins:
    Note: This is specific to Bluehost Cloud & potentially the result of their default plugin setup & unique pre-configuration that they don’t want overwritten.
    1. Akismet
    2. Jetpack
    3. Uncanny Automator
    4. Yoast SEO

Must-Use Plugins

Usually this can remain unchecked, as they are typically unique to the hosting platform & should not be migrated to another hosting provider.

Other Files

Usually this can remain unchecked

Tags , ,
Still stuck? Contact

How can we help?