Sage 100

SAGE 100 STD Upgrade from 2014 to 2017. Client using basic modules plus AR connected to JC. They bill via AR Invoice Data Entry with Customer and Jobs IDs. QUESTION: Will AR Invoice Data Entry/Sales Journal survive the upgrade? According to the 2014 to 2017 Upgrade Checklist: Pre-Upgrade Steps: ""Print and update all journals and registers. Failure to do so may result in loss of data"". This client has a large batch of unposted AR invoices. In my test conversion the batch survived the migration and data conversion. Can I expect that this will work for the final migration and data conversion?

Well, if it worked once, it ""should"" work twice or even three times. Unless it is one of those situations where Sage can't reproduce the issue. On the safe side is the fact that you aren't touching 2014. If it doesn't work at go live, you either postpone it till you have a chance to figure it out or update the AR data entry......

@JeffSchwenk Thanks for your input. I think I will set the client's expectations with: ""I believe the batch of AR Invoice Data Entry will survive the upgrade, but let's print out the Sales Journal in v2014 so we have a hard copy in case you have to re-enter those unposted AR invoices"".

I always try to have users update batches prior to the go live migration. When this hasn't been possible, existing batches have migrated and been successfully updated in 2017. The only caveat to that scenario would be invoices with credit card authorizations included. In this case I don't normally schedule the go live until I'm sure there are no unsettled credit card transactions.

In my experience, new business framework modules migrate, but I don't believe batches in legacy modules will.