Migration Failed in Free Version

@dan84, have you checked your restore log? Might be something has been changed in your site url (e.g. http or www changes could cause migration exception too). Could you please post the headers of your restore log file, so I’ll be able to analyze the situation for you.

Regards,
Lisa Breen

All resolved. But please include table prefix changes in the free version. That would have saved others and me a a lot of hustle

@dan84, see what’s the problem? The database prefix replacement requires advanced database refactoring which is a full migration as the domain name. Migration feature/logic is implemented in Pro versions. That’s why when db prefix is being changed, plugin offers either to use correct prefix if they aren’t interested in Pro version or retrieve Pro version.

well, if I had known that before I wouldnt have used the free plugin. It kind of pushes you to buy the plugin. Imagine someone without advanced wordpress knowledge? Can you explain me how he can save his backup without buying the plugin? It involves a lot of problems. Therefore I will not recommend it. Thanks

@dan84, all backup plugins function this way. Generally the migration and restoration are completely different procedures. That’s why there’re number of other plugins designed solely for migration purposes. We can allow to complete restoration anywhere, but without migrating your database simply it won’t work. It’s better to see an error or warning prior restoration, then allow you to see crashed website after restoration. Any backup tool just keeps the current working version for the specific environment and configurations. If domain or database table prefix is being changed, this requires database refactoring which is a migration. Anyway, thanks for your feedback. We’ll look into it to see how we can improve this part to make it easier for you.

Regards,
Lisa Breen