9 SAGE 1000 V 3.0UPGRADE YOUR SAGE APPLICATIONLINE 500 VERSION 7.1ENT 2.1L500 V5.0L2/500 V5.5L500 V6.0ANYTHING OLDERUPGRADE YOUR DATABASE PLATFORMSQL SERVER 2005SQL SERVER 2008SQL SERVER 2000/7.0UPGRADE YOUR OPERATING SYSTEMWINDOWS 2003WINDOWS 2008WINDOWS SERVER 2000
10 THE OLDER YOUR PRODUCT, THE MORE EFFORT IS LIKELY TO BE REQUIRED
11 PRACTICALITIES – UPGRADE FROM 5.5/6.0 Bespoke C-BASE programsTESTINGArchive TablesPayroll – MUST be on current versionDatabase Triggers & non C-BASE bespoke BEWARE POSSIBLE CHANGES TO INCIDENCE OF LOCKING
12 PRACTICALITIES – ADDITIONAL FOR UPGRADE FROM 5.0 Disaster Recovery plansUsers/passwords cleanup?Printers/Papers cleanup?Security Groups replace multiple menu systemsTESTINGXML licenceManual re-entering of stocktake card header data
13 SECURITY GROUPSRequired for DA0355 “User Access Permission views” – Sarbox requirementCreated when moving from 5.0/2.1 or olderStandard migration does one per user (!), DA0355 report goes off into orbitReorganise into logical user groups after migration and delete excess groups
14 PRACTICALITIES – ADDITIONAL FOR UPGRADE FROM PRE 5.0 TESTINGProcessing cyclesReport writer reportsRWL (aka RSL) (Report Writer Language) reportsForms – PrintMenusMessagesScreen formsWorking Directory/Database NamingRW Transfer files - Data dictionaryRW Transfer files – Data“Union” (WIP/routing) files migration to database
15 PRINT FORMS Manual migration One module/formset at a time Consider re-editing instead of migration?
16 MENUS/MESSAGES Manual migration One module/formset at a time Consider re-editing instead of migration, bearing in mind effect of security groups?
17 SCREEN FORMS Manual migration One module/formset at a time Consider re-editing instead of migration?Why? – Because old forms may not support new functionalityOld screen edits may have outlived their time!
18 BESPOKE C-BASE WORK – UNDERLYING SYSTEMS CODE Changed from Btrieve to Btrieve-removed systemsAnd again in Line 500 V5.0And again in Line 500 V5.5And again in Line 500 V6.0Not in Line 500 V7.0, but Application code will require recompilation anyway!!!!Recompilation under new source code is the minimum required, so check the cost/timescales with your reseller/developer BEFORE upgrading!
19 Processing cyclesAll batches should be postedAll modules should be at period endTHIS IS TO REDUCE THE AMOUNT OF TESTING REQUIRED AND THEREFORE KEEP THE COST DOWNThis is not mandatory for V5.0+ upgrades but is very sensible!
20 FUNCTIONALITY CHANGES MOSTLY SWITCHED ON BY ENABLING A “PROJECT”BUT SOME (USUALLY MINOR) CHANGES ARE INTRODUCED ANYWAYN.B. REDUNDANCY OF SOME SWITCHABLE PROJECTS IN LATER RELEASES E.G. DA0219“100% BACKWARD COMPATABILITY” POLICY (USUALLY!)
21 TESTING - ADVICE How much is your reseller ACTUALLY going to do? Demand to see DOCUMENTED test programme BEFORE agreeing deal!Work out which gaps YOU are going to have to testDemand to see SIGNED UP & DOCUMENTED RESULTS after migrationGET INVOLVED YOURSELF OR USE AN INDEPENDENT CONSULTANT!
22 TESTING - ADVICECheck Archives have been migrated properly (or at all!)Check spool queue items have been migrated
23 TESTING – EXAMPLESRow counts of major tables (order lines, gl transactions etc)Reprint invoices, statements etc and check layoutRun major reports (Trial Balance, Aged Debtors, FA YTD additions audit trail etc) before and after, check totals/transaction numbers agreeCheck every menu option launches without error message/popupData item processing (“Destructive testing”) on copy system
27 OTHER ISSUESChanged projects/system key settings – do this AFTER testing where possibleCopying old data to “spare” companiesBACKING UP!!!!!Do a Trial migration – particularly if you have any bespoke/externally connected systems/triggers etcMAKE SURE IT IS PATCHED UP TO DATE! (get list of program versions)
28 WHO SHOULD PERFORM THE UPGRADE? RESELLERWants your moneyINDEPENDENT CONSULTANTSee above!END USERWants to keep the moneyA COMBINATION OF THE ABOVE MAY BE THE BEST SOLUTION!
29 RESELLER UPGRADES NORMALLY DONE BY A “TECCHIE”, NOT A “CONSULTANT” FUNCTIONALITY CHANGES NORMALLY DONE BY CONSULTANTSHOULD WORK WITH AN INDEPENDENT CONSULTANTMAY MAKE THAT ROUTE “DIFFICULT”HAS A VESTED INTEREST IN DOING IT AS FAST AS POSSIBLE
30 INDEPENDENT CONSULTANT WILL BE A SAGE CONSULTANT BY CHOICEWILL HAVE IN DEPTH SAGE KNOWLEDGE, ALTHOUGH NOT NECESSARILY BREADTHLIKELY TO HAVE BEEN THROUGH UPGRADES BEFOREHAS THE “BIG PICTURE”SHOULD WORK WITH THE RESELLER
31 INDEPENDENT CONSULTANT MAY HAVE A MUCH BETTER UNDERSTANDING OF YOUR SYSTEM THAN THE RESELLERHAS A VESTED INTEREST IN MAKING IT GO SMOOTHLY AND WORK FIRST TIMEWOULD BE IDEALLY SUITED AS YOUR PROJECT MANAGER
32 END USER May be capable of some or all of the work May not have the time or inclination to do it!SHOULD get involved with testing!
33 ADVICE PLAN WELL IN ADVANCE Ask your reseller for a breakdown of the time quotedCheck they are doing adequate testingCheck the backup/DR arrangements are adequateALLOW ENOUGH OF YOUR OWN TIME FOR TESTINGPlan for changes to user visibility e.g. Paper/printers/menus/screensDOCUMENT CHANGES AND TRAIN USERS!Consider completing Upgrade and running for a period before introducing new functionality
Your consent to our cookies if you continue to use this website.