Greetings, juankpro. It sounds like you've come a very long way in just a couple of months!

Advice on how can I get a Perl partner to help me finish the tool. Specially the tests suite.

If you know what needs to be done then I'd suggest raising specific tasks as issues against your own repo and use the "help wanted" or "volunteer needed" tags. There's no guarantee of the quality of the responses but it might attract the attention of some idle hands.

Get someone to review my code so I can be confident I'm in the right path

That will be harder, not least because everyone has their own opinion on what makes good code. Ideally, see if you can garner a few reviews (from here, PrePAN, StackOverflow or wherever) and apply the recommendations which are common to all of them. For low-level, idiomatic (but still opinionated) review there is Perl::Critic.

Advice on what are the next steps or what I'm still missing to get t publish my project in CPAN

I am a CPAN author but far from a prolific one. From my experience I would recommend:

• Use Travis or another CI tool to run your test suite against a range of perl versions (there are also tools which can do this locally) as this can pick up bugs due to spec changes within Perl itself.
• Consider the various modules designed to help you produce good distros: Test::Kwalitee, Devel::Cover, Pod::Checker, etc.
• Choose what you consider to be a good name. FWIW, I don't think that "Migrate" is a fantastic name as it says nothing about what you are migrating (and it's also a new top-level which would be frowned upon especially from a new author). Maybe App::DB::Migrate or similar might be better?
• Keep re-reading the documentation at PAUSE, perldoc and here. They're full of good advice.

Good luck with your project.

(Edited to remove reference to long-gone prepan)