Sage 100

 View Only
  • 1.  v3.71 to v2013 conversion. On the surface, as ""si

    Posted 08-10-2013 09:44
    v3.71 to v2013 conversion. On the surface, as ""simple"" install and migration. But alas, their GL5 has 4.8 million transaction lines (file size is over a gig) and over 580,000 lines show up on the OOB Crystal report for correction. All appear to be part of one source journal..... Company uses GL Exchange to import transactions from 70 stores on a daily basis. Need more analysis before offering them a solution..............


  • 2.  RE: v3.71 to v2013 conversion. On the surface, as ""si

    Posted 08-10-2013 09:50
    Doesn't that OOB report have each entry that is out of balance? I think I've changed it to group by account in order to do ONE correcting entry but I can't remember how, exactly...


  • 3.  RE: v3.71 to v2013 conversion. On the surface, as ""si

    Posted 08-10-2013 10:00
    Son, You need to purge some previous years.. I would only migrate 5 year max. Copy to test purge data and repeat you out of balance report.


  • 4.  RE: v3.71 to v2013 conversion. On the surface, as ""si

    Posted 08-10-2013 10:05
    Listen to Dad...


  • 5.  RE: v3.71 to v2013 conversion. On the surface, as ""si

    Posted 08-10-2013 12:29
    I usually check the detailed general ledger by year and to see how many years are out of balance to determine how many years to keep and what needs purging. If the client needs a particular year that is out of balance, I post a one side amount to one account to balance that year. I really discourage clients from using the GL Exchange because it writes directly to the history files and can make a mess.


  • 6.  RE: v3.71 to v2013 conversion. On the surface, as ""si

    Posted 08-10-2013 19:17
    I was under the impression that each JE had to balance. I do have to figure out how recent the bad stuff is and go from there. Very bizarre as the controller claims her GL is in balance as the OOB JE's do not. I'll recalculate to see how much bad stuff happens. On top of that, they probably did a BB je to get started back in the day.... @JimWoodhead - Thanks Dad for the worldly advice. @ThereseLogeais - Does this mean you are my long lost sister???? @RonGouveia - VI is on my suggested list of module purchases..


  • 7.  RE: v3.71 to v2013 conversion. On the surface, as ""si

    Posted 08-10-2013 23:03
    I've seen GLs with hundreds of pages of OOB entries but the GL in the balance because they regularly make one sided entries to fix the OOB entries. Each GE doesn't need to be in balance but I try to get each year in balance if possible.


  • 8.  RE: v3.71 to v2013 conversion. On the surface, as ""si

    Posted 08-13-2013 11:35
    Update - Managed to finally get the transactions into my database of choice where I was able to run a pivot table. Turns out that they upload via Exchange and many times they are OOB. They then have to create adjusting entries to fix. Not sure why they don't know the JE is OOB before they import but that will be answer down stream. So the mess isn't as bad as the initial look.


  • 9.  RE: v3.71 to v2013 conversion. On the surface, as ""si

    Posted 08-13-2013 11:49
    So my next question is - If I want to try a test migration on my office v2013. Is it possible to just set up the company in 2013, then copy the 3.71 files into the 2013 data and then convert? Or does the migration utility actually do something to the 3.71 data prior to converting.


  • 10.  RE: v3.71 to v2013 conversion. On the surface, as ""si

    Posted 08-15-2013 04:47
    I created the company in v2013, activated the modules (AP, BR, GL), renamed the data folders, then copied the v3.71. Converted without a hitch. The big question is whether financials balance now...... Interesting that the GL5 detail transaction table nearly doubled in size.