A family of Microsoft relational database management systems designed for ease of use.
I don't know of another way that would be any easier. In fact, I would be very careful when using the IMPORT operations because name and other clashes require human decisions to do intelligently. For example, importing relationships might destroy existing relationships and/or create duplicates. I would take it slow and easy with a lot of thought about each object that might have any kind of interaction with the existing database. For those objects that are independent of stuff in the original database, you can select those objects and biring them in all in one shot. Besure to keep safe backups of both databases so you can revert when you find out about an entanglement you forgot to considers. I would at least consider writing a VBA procedure to do each step (probably at least the relationships) so I could rerun the parts of the import where I had ironed out the details, but later ran into something that I needed to revert and do differently.