otherwise this blows up, trying to migrate a record with no location
(the modulestore lookup throws).

Presumably this isn't (wasn't?) an issue in prod already, right?
But I did hit this in my devstack, having previously created an
LtiConfiguration record via Django Admin (without a location).