Here's four opinions on migration:

1. They are never trivial undertaking.
2. Don't think of it as just a systems project.
3. Need to stay focused on how to optimize the business
ROI (what's the business case for doing this?)
4. Do as much preparation as you can think of before starting
the weekly project team meetings. (Never fails ... if preparation
homework isn't done before the cutover clock starts ..... then
the last 6-8 weeks become a nightmare of compromises. Business
ROI opportunities end up left behind because you run out of
time to get them done well.)

More practical insights and opinions on version migrations here:

Warm regards + Merry Christmas,
Milt Habeck
Unbeaten Path
(888) 874-8008

From: Bailey, Dick
Sent: Saturday, December 04, 2010 10:39 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] 405cd to erp/lx migration

Nobody has mentioned so far what I think are the most critical issues - in
order, 1) people, and 2) customization.

Somebody said there were significant changes in how BPCS operates between
4.05 and 8.2. Well, there are some more changes between 8.2 and LX. So not
only do you have to worry through things like finding and dealing with new
validations of data (requiring new files) but also educating your people in
how the new system operates. They may have macros to change; they certainly
will have procedures to change, etc.

Customization comes in many forms - including using fields for one thing but
finding that LX uses those fields for something else, or validates them in a
way that makes your practice invalid.

You have a lot of work.

Dick Bailey
MCFA, Inc.

From: Don Cavaiani
Sent: Wednesday, December 01, 2010 7:57 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] 405cd to erp/lx migration

Some very good information from different sources already! Thank you!

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.