Prepare For Your Next Prelude Upgrade Carole Stearns

Agenda Preparation Installation Testing Go Live

epicor.com/insightsmobile Build your agenda, network, and get important event updates!

Safe Harbor Statement FORWARD-LOOKING STATEMENTS: This Presentation may contain certain statements that may constitute forward-looking statements under the Private Securities Litigation Reform Act of 1995. These forward-looking statements may include statements regarding future product releases, future functionality, revenues, cash flows, growth prospects, installed base of customers, the launch of new products and other statements that are not historical fact. These forward-looking statements are based on currently available competitive, financial and economic data together with management's views and assumptions regarding future events and business performance at the time the statements are made and are subject to risks and uncertainties. Actual results may differ materially from those expressed or implied in the forward-looking statements. Such risks and uncertainties include but are not limited to changes in the demand for Epicor's products; the timely availability and market acceptance of new products and upgrades; the impact of competitive products and pricing; the discovery of undetected software errors; changes in the financial condition of Epicor's customers; and other factors discussed in Epicor's filings with the Securities and Exchange Commission, including Epicor’s S-4 Registration Statement filed on January 11, 2012 and our future filings, including our quarterly reports on Form 10-Q. As a result of these factors the business or prospects expected by Epicor as part of this announcement may not occur. Epicor undertakes no obligation to revise or update publicly any forward-looking statements. [If you plan to say or display anything about future features, products, services, etc. that are not generally available today, then keep this slide in.]

Preparation

Prelude Upgrade: Getting Started Enter a case to be added to the upgrade list. All upgrades are scheduled 3-4 months in advance. Dates are confirmed on a first come, first serve basis. Consider any conflicts. Don’t plan anything else for the upgrade weekend. AIX upgrade, month-end, physical inventory, wedding anniversary Wrap up modifications. What accounts do we have? TEST, TRAIN, YEAREND, DAVISON

Prelude Upgrade: Getting Started Check for disk space. Update data on TEST? Perform a PSICOPY. Attend session Using SYSMAN & PSICOPY Utilities. Wednesday at 4:35 Creating a new TEST account will require additional time. TEST account is upgraded 6-8 weeks prior to go live. Moving to a new server should be a separate project.

Installation

Typical Account Structure Summit 2009: Take Action Now Typical Account Structure TEST LIVE Account Account V21-EXEC Account TEST-DATA LIVE-DATA Account Account Current SB+

Account Structure During Testing Summit 2009: Take Action Now Account Structure During Testing TEST LIVE Account Account V22-EXEC V21-EXEC Account Account TEST-DATA LIVE-DATA Account New SB+ Current SB+ Account

Typical Account Structure Summit 2009: Take Action Now Typical Account Structure TEST LIVE Account Account V22-EXEC Account TEST-DATA LIVE-DATA Account Account New SB+

System Builder and SB Client Summit 2009: Take Action Now System Builder and SB Client Version 22 will use System Builder 5.5.3. SB Client version must match. SB Client 5.4.4 or higher for Windows 7

Testing

Summit 2009: Take Action Now Testing Checklist All items on the installation modification report. All items on user menus. Any process that is mission critical. Document the upgrade testing and processes. Record any items that presented a challenge Search website cases for issues from last upgrade.

Summit 2009: Take Action Now Testing Checklist Seven types of customizations. Installation sheet modifications User Fields/User Exits Custom processes New feature retrofitted to your current version In-house EDI mapping Not changed with the upgrade Documents

Summit 2009: Take Action Now Testing Checklist Enter a separate case for each software issue uncovered during testing. Put V22 TEST Account in the case heading. This will notify us that the issue is related to the upgrade versus a problem on the live account. Provide an example. Include a comparison transaction between live and test. User-forms document formats are not changed with the upgrade.

What to Remember During Testing Summit 2009: Take Action Now What to Remember During Testing Items to update on both accounts. Menus, QRD’s, PUD’s Group & User Security, Printers, Terminals Field Definitions, Report Writer reports, screens, SB tools

Account Structure During Testing Summit 2009: Take Action Now Account Structure During Testing TEST LIVE Account Account V22-EXEC V21-EXEC Account Account TEST-DATA LIVE-DATA Account New SB+ Current SB+ Account

Go Live

Summit 2009: Take Action Now Go Live Weekend Good file save from the night before. Live account is typically upgraded on a Saturday. No users can be on the system. Average upgrade time is 2-4 hours for Epicor’s part. You will need to: Run an upgrade process /VERSION.XX Rebuild all the database indexes Restart the continuous ports and scheduler

Summit 2009: Take Action Now Go Live Weekend All field definitions, report writer reports, and screens are copied from the test account to the live account. User-forms document programs are NOT changed with an upgrade. System Builder settings on the test account are now the settings used on the live account. Group Security User Security Printers

Summit 2009: Take Action Now Monday Morning Enter a separate software case for each issue that arises. Include an example. Goal is business as usual.

Summit 2009: Take Action Now What’s the Cost? Custom installation sheet modifications. Maintenance covers a single TEST account. Any additional testing or training accounts are billable. Weekend time to perform the upgrade. Approximately $500-$1000 per account Any issues that arise related to customizations.

Summit 2009: Take Action Now Post Upgrade Previous software accounts are still on the system. Typically removed when disk space is a concern. Can be removed 2-3 months after the upgrade is complete. Enter a case requesting old software be removed Update SYSMAN with new file sets for proper file sizing.

Additional Resources Version 22 Upgrade Packet. Version 22 New Features document. Epicor website, Documentation Your software upgrade document.

Q&A