Privacy Policy Update Notice:

Sage North America updated its Privacy Policy on August 18, 2011. With this update, we made changes to the "Business Information Collection and Use by Sage" section of our policy to explain that our websites ("Sites"�) may use third party Internet advertisers that deliver custom ads to you. Such custom ads are based on information collected through cookies and web beacons when you visit our Sites. Please note that Sage does not control Internet advertisers' use of cookies or information collection. We also explain how you can opt-out of Internet advertisers' information collection. Click here to learn more. Sage North America values your privacy and is committed to maintaining your trust. Please read the full updated Privacy Policy, as you are bound by its terms when you use our Sites.

Close Privacy statement

Email this page to a Friend

Found this page interesting? Send it to your friend or co-worker by filling out this form. Add a personal message if you like.

Note: We will not use these e-mail addresses for any other purpose than sending your e-mail.


 
 

Call Sage: 866-530-7243           Privacy Policy Update Notice

Data migration should begin before ERP implementation

6/10/2011 at 11:48 am by

Enterprise resource planning software is like an enormous animal: you have to keep feeding it if it's going to stay alive and productive. The food that ERP systems are fed is data, and without that, they're nothing. Therefore, when starting up new ERP software (or converting legacy systems to newer versions), it is important to have a steady supply of data to feed a company's new creature.

Like animals, ERP systems are also picky eaters and will need the most high quality information to be healthy and productive. This means that data needs to be accurate, up to date and translated in a way that makes it easily consumed by ERP software. The best way to make sure that this is the case is to begin data collection and migration processes before implementation goes live. That way, employees can begin feeding the monster the moment it's activated. Eric Kimberling of the Panorama 360 blog offers these pieces of advice to enterprise executives.

1. Start the process early
When ERP implementation is imminent, it's never too early to start the process of collecting and preparing data. This means that a thorough examination of the types of information that ERP system will use needs to be undertaken. One way that this can be accomplished is to meet with the ERP vendor responsible for a company's implementation and determine what types and formats of data will be used by the new software. It is then possible to begin recording data in that fashion to begin a comparison of the old style and the new to develop a guide for the proper translation of information.

2. Make tough decisions
The efficiency that ERP software promises means that quite a bit of redundancy should be reduced. In fact, one of the more difficult aspects of data migration is deciding what to to leave behind when you transition to the new system. Some tough decisions are ahead for ERP administrators who want a lean and streamlined system but are reticent to let go of old data collection models.

3. Don't delegate responsibility
Above all, it is important to realize that data migration is a key aspect of making ERP implementation a success. It isn't necessarily something that can be delegated to the software vendor or low-level IT professionals within an enterprise. It will require time, money and oversight. The benefits are significant: systems will pick up where old legacy components left off, with efficiency immediately rising. However, without thorough executive involvement, data collection will become a weak point in an ERP system's repertoire.

Related Posts Plugin for WordPress, Blogger...
About the Author

Copyright / Trademarks - Privacy Policy

Email this page to a Friend

Found this page interesting? Send it to your friend or co-worker by filling out this form. Add a personal message if you like.

Note: We will not use these e-mail addresses for any other purpose than sending your e-mail.