Now that Views is in core, it behooves migrate_drupal to provide an upgrade path for any views defined in a D6 or D7 site.
Views are complicated, but it still looks reasonably straightforward to pull them from a D6/7 database and migrate them to config entities.
One complicating factor is that views can be stored in the database or in code. If they live in code, they don't live in the database. I talked briefly about this on Slack with @effulgentsia, and he said: "i think migration instructions of "get your Views (and other "features") into the db, then run migrate" is reasonable." I agree with this, but other options are welcome. One thing is certain -- views stored only in code will not be visible to migrate_drupal.
- Figure out how to handle views in code
- Write the migration(s) and tests
- Review and commit