I don’t believe banning WP all-in-one Import improves the user experience. It is my go-to for quickly taking a backup on my local host environment or migrating from one host to another.
I can appreciate that Kinsta has its in-built methods, but I far prefer the experience of WP all-in-one Import. Once I transfer what I need, I usually delete or deactivate the plugin.
Kinsta’s documentation says: “If a plugin is on our list, it’s because our sysadmin team has identified an issue with it. These problems are typically tied to performance or functionality.”
I don’t believe this to be true with this plugin, and I use a workaround to activate it anyway. It’s a slight (and unnecessary) annoyance, though.
It would be good if the Kinsta team could review the policy for this plugin again. It was banned a long time ago, and I’m sure things have changed since then.