I am working on migrating from a 14 year old in-house bug tracker to MantisBT. I see the new bug tracker as a way to get more organized about our dev, QA, and project management processes. Ideally, I would like to migrate all our old bugs into a single Mantis project (For example, a project titled 'Legacy items'), and start fresh with new projects and only move over the most recent items from the legacy items.
But, now that I am getting pushback from my coworkers to modify Mantis to look and behave more like our old bug tracker, I don't see the point of migrating as I feel that our processes will not change.
Should I push back myself to start somewhat completely fresh with Mantis? What would be the best rationale?
What is the best accepted practice when migrating bug trackers?
What is the best way to deal with a coworker who's main objection is that they can't see a list of items that have changed in a project by version number by release instead of by individual build (Even though Mantis comes with a Change log which is essentially the same thing)?