Migrating Sage300 9.7 to a new server

SUGGESTED

I am on Sage 300 CRE and Estimating 9.7 we would like to upgrade to 18.2 CRE and 18.12 Estimating.

  • We have done up a new Windows server 2016
  • Downloaded and installed Sage 18.2 CRE and 18.12 Estimating with SQL and license server
  • Migrated Database, Estimates and Addressbook from version 9.7 Pervasive to 18.12 Estimating (SQL) on the new server using the Migration tool in management console (migration seem to have gone good) able to open and use everything. (No jobcode and interface tab. )
  • Migrated the server for Accounting version 9.7 to CRE 18.2 ( seem to have gone good)
  • Migrating Data ... error locating of data folder cant be accessed ( old location points to a server no longer in existence)

Questions

  1. Why does opening 18.2 CRE desktop requires username and password? (After i have migrated the server i tried to open it)  (i try every username and password from previous use of 9.7) and it says its incorrect. 
  2. When i migrated the server it says it migrates security as well, can i migrate without the security/ delete the security after migration? 
  3. Can i UN-migrate the server to start fresh. (I know remigrating the server just replaces it. but what if i want to just delete the server i migrated completely? how would i do that?
  4. How do i get this username and password it is requesting? I cannot open any modules nor desktop without user name and password in the new version (18.2)
  5. Since 18.2 uses different database engine from estimating, could i just reinstall the Accounting aspect without it deleting my estimating?
  6. If i need to access the installation files for 13.1 where do i get them. when i click on the download , its just for an update of 13.1. but the actual 13.1 version is not on the knowledgebase.
  7. Can i set up server to mimic the one that the migration tool is referencing as the old data folder path and copy the 9.5 folder and data folders to it then just migrate the server and data from this mimic server?
  8. I migrated directly from 9.7 version of Estimating pervasive to 18.12 on a new server. Can i migrate 9.7 Accounting to 18.2 version on the new server? (so far i got past the migrating server aspect but i dont know if when i migrate the data it will be upgraded.
  • 0

    Were you able to migrate your assemblies from the Prevassive to the SQL in estimating?

  • 0

    Yes. My Estimator tested the newly migrated version and tells me they were migrated. new version is Estimating 18.12 (SQL)

    Any answers for me?

  • 0 in reply to ITCord

    We tried but never made the upgrade to SQL as our assemblies would not come across

  • 0 in reply to Vince Kolacia

    what was the error you got? which version were you migrating from and to? At firt i had an issue migrating estimates. but i stopped and remigrated. they went through

    Do you have Accounting? Can you help with the security issues im having?

  • 0 in reply to ITCord

    I'm running 300 Construction & Real estate ver 18.3.1 The user name password goes to Sage to be verified then i'm good to go. Mine will work for a limited time without internet access sort of a grace period. You made a big upgrade and maybe you missed something necessary along the way? I run the estimating on a separate computer from the accounting avoiding database conflict. Sorry not much help to you

  • 0 in reply to Vince Kolacia

    did you do a migration for 300CRE or did you just do an upgrade?

  • 0
    SUGGESTED

    Regarding your Accounting Migration - When Upgrading/Migrating from 9.7, you have to gateway install thru 9.8 and 14.1.  There were major database changes that occurred in each of those versions and were well documented in the Release Notes and User Guides.  Although you stated that it went well, I think you will end up having problems with the data going forward. As evidenced by your new server still referring to an old server location for the files.  These versions are not available on the Knowledgebase any longer and you would need to contact a Sage Consultant or possibly Sage directly to obtain these versions.  Once obtained, then I would upgrade the program files and data on your old server for both these versions.  Then migrate to 18.2 to your new server.

    1, 2, 4.  Security Issue - This could be a side effect from the improper migration from 9.7 to 18.2.  It is impossible to tell without looking at the files.  Security can be broken thru Sage or a Sage Consultant.  However. this may no longer be an issue if upgraded thru a supported path.

    3. You can uninstall Sage 300 on the current server, but I would suggest someone familiar with Sage 300 assist you in cleaning up all assemblies, registry settings and files on the system so when you migrate properly, there is nothing left of the original migration.

    I would overall suggest contacting a Sage Consultant to assist you with this project.  You are making a huge leap in major versions and a consultant would be able to help you with the pitfalls that you have encountered so far.  They would also have the skill set necessary to validate your data and ensure the upgrades/migrations happen as expected.

    Cheers,

    John McLagan
    Johnny on the Spot

  • 0 in reply to John McLagan

    Question:

    1. Can I Erase the migration of the server for 18.2 version on the new server? (I used the server migrator tool to migrate the server already, can i Undo this process?)

    2. If I removed the installation of 300 CRE and reinstalled it would this resolve the security issue so i can start fresh?

    3. Please verify if these steps would be better

    • use the install files to upgrade on current server to 13.1> 15.1> 17.1 (I can find the files for these)
    • SPin up a new server to  mimic the one the data migrator tool referenced and copy the 17.1 upgraded 9.5 folder and the data folder from the current (but upgraded ) server to the server I reinstalled 18.2 on.
  • 0 in reply to ITCord

    1. With the proper knowledge, yes.

    2. No

    3. Highly not suggested

  • 0 in reply to John McLagan

    I uninstalled 18.2. Reinstalling is showing me a greyed out software country to be United STates. I am in Canada. I have gone to windows region and location >administrative and changed country location to Canada> Restart and try reinstalling but it still uses United States as software country'

  • 0 in reply to ITCord

    Because remnants are most likely left behind.  You skipped steps in the original migration, you are skipping steps in attempting to resolve your issue.  This is not a process that someone can walk you thru step by step thru a thread.  Contact a Consultant!

  • 0 in reply to ITCord

    I have just upgraded from 13 thru 18 only skipped ver 17

  • 0 in reply to Vince Kolacia

    Did you do 13>15>16>18?

  • 0 in reply to John McLagan

    I am just reading over your answer again. Does this affect the estimating SQL version. You recommend doing upgrades first before migrating. is this recommendation also for estimating or just for accounting?