Translations

By enabling this option, Shipper can track the processing time and make sure it never exceeds the max_execution_time set by the server. The smaller the max_execution_time value, the longer Shipper will take to complete the process. <br> Shipper will skip files that are larger than 50MB. These will be logged in Shipper > Tools > Logs so you can always import those files manually.

By enabling this option, Shipper can track the processing time and make sure it never exceeds the max_execution_time set by the server. The smaller the max_execution_time value, the longer Shipper will take to complete the process. <br> Shipper will skip files that are larger than 50MB. These will be logged in Shipper > Tools > Logs so you can always import those files manually.

For a better migration success rate on large sites, we suggest that you enable the <strong>Safe Mode</strong> on the <a href="%1$s" target="_blank">settings page</a>. This will help to prevent Package Migration failure due to a constrained server

For a better migration success rate on large sites, we suggest that you enable the <strong>Safe Mode</strong> on the <a href="%1$s" target="_blank">settings page</a>. This will help to prevent Package Migration failure due to a constrained server

None of the above was helpful? <a href="%s" target="_blank">Contact Support</a>

None of the above was helpful? <a href="%s" target="_blank">Contact Support</a>

Use the <a href="%1$s" target="_blank">Package Migration</a> %2$s

Use the <a href="%1$s" target="_blank">Package Migration</a> %2$s

Looks like a long time? That’s because the API method causes no load to your server and is super reliable. If you’d like a much quicker migration, use the Package Migration method – you can upload a package of your site onto any server (local or live) and be migrated in a matter of minutes.

Looks like a long time? That’s because the API method causes no load to your server and is super reliable. If you’d like a much quicker migration, use the Package Migration method – you can upload a package of your site onto any server (local or live) and be migrated in a matter of minutes.

To migrate a <strong>local site</strong> here, initiate the export from the local site.

To migrate a <strong>local site</strong> here, initiate the export from the local site.

You can export the <strong class="subsite-slug">%s</strong> subsite to any other single site connected to the Hub.

You can export the <strong class="subsite-slug">%s</strong> subsite to any other single site connected to the Hub.

As a security measure you'll need to confirm your WPMU DEV account to continue. Please enter the password for your connected account <strong>(%s)</strong> or authenticate with Google.

As a security measure you'll need to confirm your WPMU DEV account to continue. Please enter the password for your connected account <strong>(%s)</strong> or authenticate with Google.

Oh no! Looks like the Pre-flight process is stuck for the API Migration method. Please cancel this process and try the <a href="%s" target="_blank">Package Migration</a> method instead.

Oh no! Looks like the Pre-flight process is stuck for the API Migration method. Please cancel this process and try the <a href="%s" target="_blank">Package Migration</a> method instead.

Your website is %1$s in size, and <strong>the final archive could be somewhere between %2$s to %3$s</strong> depending upon the type of files on your site and the compression rate possible with them. If you haven’t already, you can try excluding larger files to speed up the package build.

Your website is %1$s in size, and <strong>the final archive could be somewhere between %2$s to %3$s</strong> depending upon the type of files on your site and the compression rate possible with them. If you haven’t already, you can try excluding larger files to speed up the package build.

Also, please note that the package build time may vary considerably depending on factors such as the speed of your current host and your package migration settings. So, for a better migration success rate on large sites, we also suggest that you enable the <strong>Safe Mode</strong> on the <a href="%1$s" target="_blank">settings page</a>.

Also, please note that the package build time may vary considerably depending on factors such as the speed of your current host and your package migration settings. So, for a better migration success rate on large sites, we also suggest that you enable the <strong>Safe Mode</strong> on the <a href="%1$s" target="_blank">settings page</a>.

There was an error while trying to build your package! For better chances at succeeding, we suggest that you enable the <strong>Safe Mode</strong> on the <a href="%1$s" target="_blank">settings page</a> and try creating the package again. If you are unable to solve the issue, you can also try the <a href="%2$s" target="_blank">API Migration</a>, our alternative migration method.

There was an error while trying to build your package! For better chances at succeeding, we suggest that you enable the <strong>Safe Mode</strong> on the <a href="%1$s" target="_blank">settings page</a> and try creating the package again. If you are unable to solve the issue, you can also try the <a href="%2$s" target="_blank">API Migration</a>, our alternative migration method.

<strong>%s</strong> is a multisite network, choose which subsite you want to import as a single site.

<strong>%s</strong> is a multisite network, choose which subsite you want to import as a single site.

Not sure how to use them? Refer to our <a href="%s" target="_blank">file exclusion docs</a>.

Not sure how to use them? Refer to our <a href="%s" target="_blank">file exclusion docs</a>.

Select the <strong>Advanced</strong> tab to access a list of options that allow you to exclude some seldom-used files maintained by WordPress. These include:

Select the <strong>Advanced</strong> tab to access a list of options that allow you to exclude some seldom-used files maintained by WordPress. These include: