Jay and I talked about this, and I went back and forth on it. I think our db collection names in this area are stable enough to go ahead and use these. Looking at other migrations, if we change the names or how we connect to the db or anything else that low level, this migration script will be the least of our worries.

What we really need is a migration-specific Pulp API that holds the contract of being forever backwards compatible. Plus, there's a real disconnect here: Pulp migration scripts are not necessarily in lock-step with pulp_rpm migration scripts, so if a pulp migration script changes a db name, what versions of pulp_rpm migrations use the old vs the new? Of course, this problem isn't limited to pulp_rpm

I'm going to leave them as is.