Try performing a full build and optimize of the PBLs in PB 12.5 before migrating.  

If your app uses PFC, please make sure you follow these tips: https://youtu.be/1qhbFDJvx3M?t=23m19s

If the problem still persists despite trying various suggestions, please open a support ticket and upload the PB 12.5 PBLs so Appeon engineers can analyze the cause: https://www.appeon.com/standardsupport/newbug

Hello i am having the same problem, i replace the pbsoapclient120 to pbsoapclient170 but i got the crash engine.

Have you found the solution?

Hi, 

1. Have you optimized and full built these PBLs in PB 12.5 IDE before migration? If you haven’t, we suggest that you try it.
2. Use PB 2017 Migration Assistant to load your PB 12.5 PBLs and see if there is any error. If there is any, please handle it first.
3. Are you using any PBD or PBX (PBNI), if you do, please make sure you are using the matching version for PB 2017, such as pbsoapclient170.pbd, pbejbclient170.pbd, pbwsclient170.pbd, etc.
4. Did you have both PBLs from PB 12.5 and PBLs from PB 2017 in PB 2017 Library List when it crashed during your migration? We suggest that you put all your PB 12.5 PBLs together as a small PB 12.5 application, and then use PB 2017 to load this application’s PBT, and see if you get any errors migrating this way. If everything goes well, you can then load these migrated PBLs in PB 2017.
5. If you have a PB 12.6 environment, you can try migrating to PB 12.6 and then to PB 2017.
6. If you still can’t resolve the issue, please open a support ticket at https://www.appeon.com/standardsupport/  and provide sample code that can reproduce the issue for us to analyze.

Regards, 

Ken