There are few common causes related to maven migration
- Your project consists of many internal dependencies (artifact created by yourself / colleagues) stored on your PC maven repository cache, as opposed in a shared internal repository. When you migrated into new PC it's no longer able to resolve these
- Your company has an internal maven repository (eg: nexus) and your project pom.xml isn't configured to search for this repository
- Your project is a multi module which aren't setup very neatly such that the topmost artifact in the dependecy map has to be installed first on your local repo before others can pull it
- Your new pc repository use different maven version / jdk version combinations
Your pc local repo is normally located at ~/.m2/repository