Transcript Example Presentation
Upgrading to v3.0
and beyond
Sage User Network, 18-19th October Dr Janet Bastiman
Version 3 – big changes
• • • • Resign of some parts of the architecture Opportunity to update hardware Migrate to a common starting point and then upgrade Make updates easier • Most of all – ensure that user upgrades are as smooth as possible
2
Key areas
• • • • • FCEs, client automation will work on webclient Layout manager redesigned and formset wizard added RS/RWL reports will work with new report format Minor underlying data structure changes Mandatory projects change
3
Migration Details
Existing System
Sage 1000 v2.3
V3.1 ERP only
Line 500 7.1
Line 500 7.1 with SLX over AIS Line 500 7.1 and non integrated Sage CRM Line 500 7.1 and non integrated SLX Sage ERP 1000 v3.0
Sage ERP 1000 v3.0 and non integrated SLX Sage ERP 1000 v3.0 and non integrated SCRM SCRM 6.2
SLX 7.5
• • • • • • •
V3.1 with SCRM
• •
V3.1 with SLX
• • • • • • • • • •
4
Scenarios
• Line 500 v6 GUI client to Sage ERP 1000 v3 Web client • Holistic considerations: training, look at business practises – could you make use of new features to streamline operations?
1.
2.
3.
4.
5.
6.
Install L500 v7.1 over v6 Check customisations and add-ons Resolve any issues Use Sage ERP 1000 v3 installer over Line 500 v7.1
Check customisations and add-ons Resolve any issues
5
Scenarios
• Line 500 v5.0 to Sage 1000 v3.0
• Holistic considerations 1.
2.
3.
4.
5.
6.
7.
8.
9.
Use L500 v6.0 over Line 500 v5.0
Check customisations and add-ons Resolve any issues Use L500 v7.1 installer over Line 500 v6 Check customisations and add-ons Resolve any issues Use Sage ERP 1000 v3 installer over Line 500 v7.1
Check customisations and add-ons Resolve any issues
6
Best Practise
• • Back up regularly Separate test server – not just for upgrades but also for patches, customisations, third party products before going onto live system • Recreate business practises – Even the uncommon ones!
• Ensure all customisations are tested
7