Sage 100

 View Only
  • 1.  Upgrading a client from v4.05 to v2016, sorry do n

    Posted 05-05-2016 10:25
    Upgrading a client from v4.05 to v2016, sorry do not know whether it will be Std or Adv. My concern and wandered what others thought... This client has not closed any modules for 2015 and want to wait until after upgrade. My gut says they should at least close up to Dec 2015 (may not have all their taxes done yet), mostly because the new business framework, but do not see anything that really backs this thought process. Thoughts?


  • 2.  RE: Upgrading a client from v4.05 to v2016, sorry do n

    Posted 05-05-2016 10:32
    Interesting question and I'm curious of other's answers as well. One school of thought might be that if you don't close PE there is probably more data available for Sage to convert to the new history tables now available in framework. Thus the client will get some additional historical information that might get lost if the do PE closing prior to the upgrade.


  • 3.  RE: Upgrading a client from v4.05 to v2016, sorry do n

    Posted 05-05-2016 10:33
    of course the other side of that coin is that there is more data to convert so it will take longer and there is more risk of corrupted data.


  • 4.  RE: Upgrading a client from v4.05 to v2016, sorry do n

    Posted 05-05-2016 11:48
    Will you do a ""pilot"" or ""test"" migration of the data in advance? In the Non Framework Subsidiary Modules, (assuming they are not closed); you will not have any ""definition"" of what is in the current month, and one future month. I'm wondering what the upgrade will do with all the ""future transactions"" bunched together in the one future period. Will the upgrade break them out by month? I would probably migrate the company as is, and a copy of the company with the periods all closed to 12/2015; to see the results.


  • 5.  RE: Upgrading a client from v4.05 to v2016, sorry do n

    Posted 05-05-2016 12:30
    I always insist that customer closes the periods for all modules to at least the prior month and let them leave GL open to last period of prior year. Its not an option with me, they should close the periods on a regular bases to prevent posting to what should have been a closed period. I also prefer that they restrict posting to current and one future period. How many times have we had to deal with a fat-fingered date ending up creating records far into the future.