Hi @chadreitsma,
I can see why that looks like the obvious solution. Here’s why we didn’t go that route:
We believe that migration profiles should have smart defaults that allow the user to create a new Export and immediately run the profile without error. This was not the case with the old approach because leaving the URL and Path fields empty would result in validation errors, which led some users to believe those fields were required. Furthermore, they didn’t know where to find the path info at their destination.
The new optional approach provides the same benefits without the validation errors, and is more consistent with how these fields are presented during Push and Pull migrations. This makes the export workflow more accessible to a wider variety of workflows since some users just want to do a clean export without modifying those values.
Just to clarify a note from your other review, our team at WP Engine includes the exact same folks from Delicious Brains. While we may make a an occasional misstep, I assure you we’re just trying to do the right thing for our users. We are listening and reacting to feedback as we always have. Since joining WP Engine, we have added new value by expanding the free export functionality to also include site files, and we have no plans to hide any existing functionality in the Lite plugin behind a paywall. I hope that addresses some of your concerns, and thank you for the feedback.
