Sage 100

3.71 to 2018 with a stop at 2017. Using the @BillPfahnl approach. Migrated data to 2017. Start data conversion. Last entry in the Activity log before the error is the CI conversion. Anyone run into this issue? Hold the fort . . . restarted the conversion and it isn't bombing again . . . at least, yet.

I just did one of these and I had to stop at 4.30 first and then convert to V2017. Did you try that?

Yes I have done several upgrades and always go through 4.30 from anything that old. Also did a few 4.2 to 2018 and did a pass through 2016 first.

No, after I restarted the conversion, it finished.

Good to know. Sage recommended 4.3 pass so that is what I have always done.

I didn't know Sage was making that recommendation. Good to know.

It just bit me. Inventory didn't migrate properly. Item codes got created, but no data. looks like I have to start over with a different stop. @KelleyJohnson1 if you go through 4.3, do you have to make another stop at 2017, or just 4.3 to 2018?

You must go though one of these versions V4.50.8 to v2017 prior to V2018. my recommendation id V3.71 to V4.30 to v2017 to V2018

So if you go to 4.3, you don't have to stop again at 4.50.8?

you need to stop at one of these versions between V4.50.8 and v2017 ( any one them will work.) prior to V2018 I think V2017 is the easiest.. V2018 required it come from one of those versions

Are the rules the same if you are not using inventory?

Do you have to install 4.3 or just copy it up and run it (mas90 style)?

you can copy a version up but you will need to have it match the configuration so you can migrate the system file the first time.

@WayneSchulz I usually stop v4.30 if I am converting from V3.71 or lower. If you are already on V4+ you likely can go direct to V2017. though YMMV

I copied up my local 4.3, but it won't accept their 2018 keys. What keys do you use?

I use my own keys since it is just a temporary install if the user keys don't work. I always do same steps as @JimWoodhead

Thanks @KelleyJohnson1 !