Sage 100

 View Only
  • 1.  Working on SAGE 100 STD v2013 upgrade to v2016c. C

    Posted 09-08-2016 11:17
    Working on SAGE 100 STD v2013 upgrade to v2016c. Client has a ton of UDFs and custom CR forms. Performed a test upgrade (30 days ago) and client reported that all UDFs and CR Forms look good in v2016. Ready to perform final upgrade (from current v2013 data) this weekend. Client reports that new UDF's have been added in v2013 since the test upgrade (where both system and data files were migrated and converted). Will the new UDFs that were added in v2013 be migrated and converted during this final upgrade (data files only are migrated and converted)?


  • 2.  RE: Working on SAGE 100 STD v2013 upgrade to v2016c. C

    Posted 09-08-2016 11:28
    I am posting against this because I would like the clarity as well. So... Just here for the comments.


  • 3.  RE: Working on SAGE 100 STD v2013 upgrade to v2016c. C

    Posted 09-08-2016 11:29
    User defined fields are copied during a ""SYSTEM"" migration and not during a company data migration. You could use Custom Office to export all the UDF and UDT definitions then import those definitions to the new system prior to the data-only migration. That way the new table definitions will be in place to receive the UDF values.


  • 4.  RE: Working on SAGE 100 STD v2013 upgrade to v2016c. C

    Posted 09-08-2016 11:44
    When adding fields mid-migration like this we make a habit out of doing the changes to both systems at the same time.


  • 5.  RE: Working on SAGE 100 STD v2013 upgrade to v2016c. C

    Posted 09-08-2016 11:55
    Thank you @PhilipWhirley and @KevinMoyes Since the test upgrade went very well and all UDFs and CR Forms came over with no issues, can I perform the final upgrade by migrating BOTH system files and data files? Should I delete the test upgrade (destination) and start from scratch.


  • 6.  RE: Working on SAGE 100 STD v2013 upgrade to v2016c. C

    Posted 09-08-2016 12:09
    Remigrating both system and company data should be fine without starting from scratch. To save time reconverting the report files you can copy them somewhere safe and bring them back afterwards (unless there have been changes to them mid-migration).


  • 7.  RE: Working on SAGE 100 STD v2013 upgrade to v2016c. C

    Posted 09-08-2016 12:22
    I do not believe it is necessary to start from scratch. As Kevin says, you can remigrate system and data into the existing instance. HOWEVER, if you have third party modifications of any sort, you will need to reinstall them after you re-migrate system files. This is not necessary if you just migrate company data.


  • 8.  RE: Working on SAGE 100 STD v2013 upgrade to v2016c. C

    Posted 09-08-2016 12:36
    Don't forget, any changes to Security Roles done in new v2016 will be lost if you Re-Migrate System Files.


  • 9.  RE: Working on SAGE 100 STD v2013 upgrade to v2016c. C

    Posted 09-09-2016 15:08
    Thank You @MadelineStefanou the client told me they made changes to the Security Roles too. Looks like I re-migrate System files and re-install 3rd party enhancement. Thanks for all the replies.