Moving to Epicor ERP version 10: Experiences so far Presented By: Adrian Anastas (Precise Business Solutions)

Agenda Introduction Preparing for the Upgrade Upgrade Steps Customisations Q&A

Introduction Who is on 10? 10.1? 10.1.500? Who is thinking about it?

Preparing for the Upgrade

Planning & Preparation Considerations Why are you doing the upgrade? Who will be involved? How long and how much effort will it take? How much change is expected & how will it be managed? WHY is important – it will drive decision making as it relates to everything else especially budget and timeframes and that in turn will drive scope - take Advantage of new Features – 10 Reason to upgrade (https://epicweb.epicor.com/resources/MRCPartners/Epicor-ERP-10-Reasons-to-Upgrade-A4-ENS.pdf) Performance Stability Functionality: Bank Recs, statistical accounts, Global COA Ease of use Epicor Web Access Epicor Social Enterprise/Collaboration Easier Upgrade path Cloud ready Epicor Commerce Connect Enhanced Tools - Old Hardware needs refreshing - Pressure to be more efficient/competitive -Risk Management/Datarecovery WHO is important – how many people, what roles do they play, what is their availability, do they support the WHY HOW long and HOW much time and effort will it take: Example of DB upgrade taking 7 days. Typical to take an entire working day CHANGE – environments, functionality, design, acceptance, timing New Hardware: If already on 9.05.70x you should be OK with what you’ve got. But this will be a site by site evaluation.

Upgrade Steps

Epicor ERP version 10 Upgrade or Migration Manage Readiness Coordination Project Management Upgrade Test Installation Database Upgrade Process Review Gap Analysis Customisation Uplift Migrate Data Extract / Import Import/Redo Custom Test/Train Configuration & Testing Proof of Concept Core Team Training User Acceptance Testing Cutover Live Installation Go Live Support First Month End Close Depending on your starting version, you will either be upgrading, or migrating. That means as a Vantage customer, assuming you are on 8.03.409 or above, you can upgrade. If you are an Enterprise or Scala client you will be migrating. The key difference between the two is how we handle existing data. An upgrade will bring existing data forward into the new version. A migration means you bring forward opening balance and masterfile data only. If you are a progress client, the database upgrade process will also include conversion to SQL. From Enterprise Data Extraction Use Data Extraction Tools (available on latest versions) Export via eIntelligence/Explorer (any version) Create custom export scripts (any version) Configure 10.0 Import via Data Management Tool (10.0) Progress Sites – see Chapter 6 of the E10_MigrationGuide_Progress_100600.pdf on EpicWeb The source database must be Progress version 10.2A At a minimum, SQL Express 2008 or SQL Express 2012 must be installed on the server where Progress OpenEdge is running

Pre-requisites Post everything Back Up Back Up again Test Test Again

Progress to SQL Conversions Epicor 9.05.702A PROGRESS Epicor 9.05.702A (Interim) SQL Epicor 10.X SQL Progress version 10.2A Review truncation & skipping rules Support Downloads: Migration Guide from progress OpenEdge to Epicor 10 (Chapter 6/7) During the data transfer processing, data may be truncated or skipped due to any existing data overflow conditions. It is recommended that you run a preliminary migration on your Test or Pilot Epicor 9.05.702A database to find and resolve any data issues prior to migrating your Production database to Epicor 10. TXT files will be generated containing the data that was truncated and/or skipped. You need to resolve these in your production database and redo the process in order to proceed. The rules are listed in Chapter 6 of the Migration Guide document.

Upgrade Steps If pre 9.05.702A, Interim Upgrade Prepare Hardware Upgrade to 10.1.500 Post Migration Checks Dashboards Reports BPMs Posting Rules Custom Epicor 9 to Epicor 10 Migration Utility Document - A Simple Flow! http://www.epicorusers.org/p/do/sd/sid=572 New Hardware needed? SQL Server Required/upgraded? Post Migration Checks Dashboards: Usually Works fine Reports SSRS: A curse and a blessing. Conversion utility is hit and miss BPMS: Will be created deactivated: Suggest modified to C#/LINQ Posting rules take a couple of times to import Custom/UD fields will be renamed

Customisations

Options for Customization Uplift Do it yourself Training Consultant does it all Run program against database; obtain results Use tool provided by development to uplift customisations Good for those knowledgeable about C# Run program against database; submit results Participate in hands on training conducted with one of your customisations Additional assistance available as needed Run program against database; submit results Consultant provides quote based on scope of effort Good for those with numerous or complex customisations; no in-house C# experience Utility to migrate Crystal Reports: Hit and Miss

Customization Upgrade Elements Standard UD fields converted to Extended UD fields Wizard driven BPMs upgrade seamlessly Advanced BPMs (ABL code) require separate conversion All BAQs upgraded BAM/Global Alerts/Autoprint converted to Data Directives Configurator – rules needs to be rewritten Even though Wizard drive BPMs and BAQs upgrade it still makes sense, with the changes in the tool set, to revisit what you’ve done and review to see if there are better ways to do it All ABL code needs to be converted to C#

Thank You! Questions?