Welcome, Guest
Username: Password: Remember me

Poll: Overall was it easy for end users to adapt to ES?

Yes No Problem No votes 0%
Some Problems, Training Took Care Of 4 100%
Difficult, Did Not Want To Adapt No votes 0%
Total number of voters: 2 ( Kruegeme, pjohnson )
Only registered users can participate to this poll

TOPIC: Moving from Progression to ES

Moving from Progression to ES #282

  • johnfitz
  • johnfitz's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 7
  • Karma: 0
Hi - we are a manufacturer in Central New York - We are in the process of evaluating our first integrated database (combine Macola Progression/Esyn for upgrade to ES.) My question - if anyone has gone from Progession 7.6.3to ES how did it go? What kind of problems did you encounter, what might be done differently?

Or was it better than you expected? I am in the process of comparing data/reports between the two versions to ensure that financials match etc...Also have some data scrubbing to do.

Greatly appreciate any feedback/advice you can give.

Many Thanks!
The administrator has disabled public write access.

Moving from Progression to ES #283

  • Kruegeme
  • Kruegeme's Avatar
  • OFFLINE
  • Expert Boarder
  • Posts: 91
  • Karma: 0
We are a custom manufacturer in South Central Texas. We upgraded from Progression 7.5.103f to ES with eSynergy over the July 4th weekend. We started the upgrade process on Thursday, June 30th. Due to some unknown issues it failed, we started the second conversion on Friday, July 1st, then the third try again later on Friday. The fourth conversion was a success and finished on Sunday. Our SQL server was a dual 600 with 4 gig ram and it took about 4 times longer than Exact single processor 2.4 gig test system to convert the 30 gig database.

Post conversion was a little tramatic for some of the users, mainly A/R and A/P people as their life changed dramatically. I would suggest that you have a consultant onsite to walk through their daily process with them again after conversion as the preconversion training helped but it didn't sink in until they actually tried to work in it all day long. We also had some performance issues which have since been addressed in recent program upgrades.

If you write a lot of Crystal Reports as we do, you have to take a step back and look at the new links but once you get those down its not too bad.

Overall, the conversion of ES has not had any significant issues in our organization. We are rolling out eSynergy to the different groups now and are modifing some of our business processes to take advantage of the new system features.

Not sure how you handle your sales force but you might want to take a close look at commissions are handled and how salespeople are setup in ES so that's not a post conversion surprise. We had around 1500 salespeople defined in Progression so a lot of post conversion time was spent deactivating those resources and verifing that the resource and salesperson records tied correctly (ours had to be tweaked).

Good luck,

Marc
The administrator has disabled public write access.

Moving from Progression to ES #284

  • Kruegeme
  • Kruegeme's Avatar
  • OFFLINE
  • Expert Boarder
  • Posts: 91
  • Karma: 0
We are a custom manufacturer in South Central Texas. We upgraded from Progression 7.5.103f to ES with eSynergy over the July 4th weekend. We started the upgrade process on Thursday, June 30th. Due to some unknown issues it failed, we started the second conversion on Friday, July 1st, then the third try again later on Friday. The fourth conversion was a success and finished on Sunday. Our SQL server was a dual 600 with 4 gig ram and it took about 4 times longer than Exact single processor 2.4 gig test system to convert the 30 gig database.

Post conversion was a little tramatic for some of the users, mainly A/R and A/P people as their life changed dramatically. I would suggest that you have a consultant onsite to walk through their daily process with them again after conversion as the preconversion training helped but it didn't sink in until they actually tried to work in it all day long. We also had some performance issues which have since been addressed in recent program upgrades.

If you write a lot of Crystal Reports as we do, you have to take a step back and look at the new links but once you get those down its not too bad.

Overall, the conversion of ES has not had any significant issues in our organization. We are rolling out eSynergy to the different groups now and are modifing some of our business processes to take advantage of the new system features.

Not sure how you handle your sales force but you might want to take a close look at commissions are handled and how salespeople are setup in ES so that's not a post conversion surprise. We had around 1500 salespeople defined in Progression so a lot of post conversion time was spent deactivating those resources and verifing that the resource and salesperson records tied correctly (ours had to be tweaked).

Good luck,

Marc
The administrator has disabled public write access.

Moving from Progression to ES #662

  • PaulO
  • PaulO's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 6
  • Karma: 0
We are a mfg of brake pistons in Central NY. We used 7.6.300 and eSynergy. We also dod a conversion over the fourth of July. the first one failed because some one VPN'd in from home "just to check on things" and when they signed into 7.6.300 it blew. I shut down all PC's and restarted conversion and it finally went.

Our biggest problem was we have several customers that have more than one customer ID in 7.6. The reason is each ship to location has their own lock box hence the need for separate ID's. We had work flows and documents along with 7.6 data for each customer. Our test conversions highlighted ther need to match up the esynergy and 7.6 ID's AND customer names for the DB merge to link them up properly. Exact gave us match-up queries, we did a lot of data scrubbing, but in the end it cocked up anyways.

We had to spend a lot on time having Xonitek Systems come in and write SQL queries to straighten out the workflows and documents. You see, it DB merge can't make a match, it assigns a new customer number and away you go. We had ES data in one place, and workflows in another, neither of which are in the old customer numbers. It was quite painful but we fixed it.

The cash flow applications and match processes are quite different than 7.6. The accounting staff likes it now but it was all new in the beginning. We had to get used to the new reports and screens but in the long run we think it was worth it.

And now when we view a customer in eSynergy, ALL the financial data, orders, forecasts, along with documents and work flows are in the same place. That is a beautiful thing.

Also, financial statements - you can put data into ES broken out by GL account number and department, but the ES statements cannot break them out. You either run statemetns with a filter turned on (one run for each department), or use an Excel add-in to write your own. the built in statemetns take 30 seconds or less to run which dumps the output into Excel. Our excel add-in version takes 5 minutes to run (which is good giving the number of individual queries in the bloddy thing). Our CFO is not very happy with the time difference so now we are looking at Exact Business Analytics and possible writing our own statements using VBA or something.

And I suggest everyone build a test server and plan about 6 months to a year of testing and oreintation. The tough part is training people and expecting them to remember after a few months. Do initial training and then follow up training a week or two before conversion.

The converison program is pretty powerful. We used it to change our GL account structure. N o programming invilved. Its all wizard based. Pretty slick.

Other than going over budget a bit on the conversion costs, I would say it went ok. Just do it, get it behind you, and move on.

Paul Orr
Diemolding Corp
Paul.Orr@Diemolding.com
The administrator has disabled public write access.
Time to create page: 0.039 seconds
Powered by Kunena Forum  Protected by R Antispam