1) The more detailed your testing and training efforts are, the better the final outcome. It is best to take a few typical organizational units that would cover over 80% of the types of transactions you have and do a thorough test before jumping in to the organization-wide implementation.
2) The creation of Mapping tables is critical to ensure data consistency. A lot of effort needs to go here.
3) There needs to be a lot of communication and these needs to start very early. There will be plenty of resistance to change (surprise!) The objective is to overcome people’s fears and give them information and training in advance to get their buy in.
4) All levels of Management need to have the same objective – i.e. successful implementation. If one does an Accounting only implementation, there will be no participation from Management – the result will be sub-standard.
5) Clear directions on transition to the new system. How will one handle incomplete transactions in the old system? What is the cut off? What history will be carried to the new system?
6) On line – web-based help for various processes. Training needs to be a mix of class room, on-line (web based) and help info if one gets stuck.
7) Minimize the customization as far as possible – that will mean complications when you go to the next version.
8) Look at reports carefully. What reports are essential? Can these be downloaded to excel? Can you get PDF reports? Make sure that these are catered for. This is usually a big frustration for people learning/using a new system – the reports do not give the information required.
9) Depending on who will support the application, we need to ensure that there is a long enough transition from the people who implement / configure the system to the people who will support / maintain the system. Many times, the implementation is done by consultants (highly-paid of course), who vanish after the implementation is done leaving a big knowledge gap.