"Class no longer exists" after migration module is disabled

Your migration module should deregister its migrations in hook_disable() - see migrate_example:

function migrate_example_disable() {
  migrate_example_beer_disable();
  migrate_example_wine_disable();
}

function migrate_example_beer_disable() {
  Migration::deregisterMigration('BeerTerm');
  Migration::deregisterMigration('BeerUser');
  Migration::deregisterMigration('BeerNode');
  Migration::deregisterMigration('BeerComment');
}

In the latest dev you need
drush ev "MigrationBase::deregisterMigration('NAME');"

Suggested solution didn't work for me, but ...

It turned out that for me there were items left in the migrate_status table after uninstalling the example migrate module. (It's also possible that they were added during development when I used one of the example modules as the start point of a migration - so don't treat this as a bug report.)

Anyway, the solution was to go into mysql, and delete the rogue entry...

delete from migrate_status where machine_name="WineProducerXMLPull";

Problem solved.

Confirm suggested solutions don't work. And actually, I would call this a bug.
Thanks for suggestion, Jeff. I was about to start sifting through the DB to find the errant class...

If I understand this correctly, if you rename/remove a class from your migration you will need to add in a Migration::deregisterMigration('MyOldClass'); for each of them, and then disable and re-enable the module in order to remove the excess tables, records and error messages? Unless I'm mistaken, this seems unnecessarily complicated.

What if the "no longer available" classes were still visible in the UI, but were greyed out and with an option to de-register them... would there be any problem with that?

Please don't reopen closed issues, open a new support request in such cases.

There is now a drush migrate-deregister command:

drush migrate-deregister Article # To deregister a given migration
drush migrate-deregister --orphans # To deregister all migrations whose class no longer exists

The last command in #10 cleared the situation and successfuly deregistered all the stuff.

BTW, the demo module included in migrate_d2d doesn't deregister its classes, which lead me there.

Seems like this issue still persists. However, the problem can be mitigated, as suggested by @Jeff Veit. You can go ahead and delete the specific class name from the DB Table "migrate_status" for the time being.

#10 also worked for me. Thank you.

#10 drush migrate-deregister --orphans worked for me and I am using migrate_d2d project, thanks mikeryan!

Thanks Jeff !!! #7 worked for me. But it is also good idea to De-register the classes which are not in use in .install file in hook_disable() itself. Using #10 drush migrate-deregister is clean way to do the same. :D

Cheers,
PrathK
extrimity.in

Deregistering the errant classes using hook_disable(), was not working for me. I ran the following Drush command, and that appears to have cleaned up the issue.
drush migrate-deregister --orphans

drush migrate-deregister --orphans worked for me. Thanks.

#10 drush migrate-deregister --orphans worked for me with a class extending migrate_d2d. Thank you!