Thanks for the feedback Phil and Jim.
This is a test migration... not going Live until late next week. Progress (after uninstalling 2018):
- Installed 2016.0 Standard (partner keys, choosing the right modules)
- Installing 2018.5 Premium (customer keys)
Next steps:
- Migrate to 2016.
- Company data conversion (5 company codes, and not a high volume of data).
- Migrate to 2018.
When it comes to Go-Live, I'll probably repeat the steps... as long as the test goes well.
*fingers crossed*
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------
Original Message:
Sent: 03-14-2019 17:59
From: Jim Woodhead
Subject: Upgrade 4.4 Standard to 2018 Premium... middle step (no PR)
I have had mixed results with it... I think it all depends what version your coming from. It can't hurt to test it. If you are remigrating or have a failure.. Make sure you delete the MAS_XXX table in SQL prior to remigrating and replace the entire MAS_XXX on the PVX side. The conversion will handle all the migration into SQL.
Original Message------
I've never tried just moving the data without actually upgrading it in a middle step. I suppose you could see if you get the same "must be version 4.50" message.
------------------------------
Phil McIntosh
President
Friendly Systems, Inc.
Asheville NC
678.273.4010 ext 5
------------------------------