Migrating from Macola ERP to a New Modern System: A Step-by-Step Guide
- Roger Pujol, CPIM, CSCP
- 5 days ago
- 3 min read
Updated: 2 days ago
Introduction: Migrating from an older ERP like Macola (Progression or ES) to a more modern system can unlock new efficiencies, improve scalability, and reduce technical debt. However, ERP data migration is a complex and critical process that must be handled with precision. In this blog, we'll walk you through the essential steps to successfully migrate from ECI Macola ERP to another ERP system.
Depending on the ERP system you are migrating to, certain Value-Added Resellers (VARs) might already possess proprietary and exclusive tools to facilitate a smooth migration. Similarly, independent ERP consultants like Champion Business Solutions, LLC, have developed their own proprietary and exclusive data extraction tools.
1. Define the Scope of Migration: Start by determining exactly what data needs to be migrated:
Master Data: Chart of Accounts, Customers, Vendors, Items, Bills of Materials
Open Transactions: Sales Orders, Purchase Orders, Inventory (Location and bin), AR/AP balances
Historical Data: Invoices, Shipments, Payments, and more (optional, often archived)
Clarifying the scope helps in setting realistic goals, timelines, and budgets. It is important to note that open production orders are typically burned down and not migrated.
2. Analyze and Map Macola Data: Macola stores data in a SQL Server database with tables such as OEORDHDR (Sales Order Header), OEORDLIN (Sales Order Lines), and IMITMIDX (Inventory Items).
Steps to follow:
Extract a schema and create a data dictionary.
Map fields from Macola to the new ERP's structure.
Note Macola-specific conventions such as status codes, unit of measure formats, and custom fields.
3. Extract Data from Macola: Using SQL Server Management Studio (SSMS) or another database tool, extract data via SQL queries. For example:
SELECT * FROM OEORDHDREnsure that relational integrity is maintained and that related data (e.g., orders and order lines) are extracted together. This is also the point where you decide how much data to bring over. We have seen clients with over 25 years of data.
4. Transform the Data: Data transformation ensures compatibility with the new ERP. This involves:
Data Standardization and Cleanup (click here to see our blog posting)
Converting codes and statuses
Standardizing formats (dates, currencies, etc.)
Cleaning or archiving obsolete/custom data
ETL tools such as Talend, Pentaho, or Power Query in Excel can help automate this step.
5. Load into the New ERP: Depending on the new ERP system, use appropriate loading mechanisms:
CSV Import Tools: For systems like NetSuite, Business Central
APIs: For cloud-native platforms
Middleware/Integration Tools: Such as KingswaySoft, Celigo, or Boomi
Make sure to load in logical sequences (e.g., load customers before invoices).
6. Validate and Test: Thoroughly validate the data:
Reconcile financials (trial balances, inventory totals)
Confirm master data accuracy (addresses, terms, GL accounts)
Perform functional testing with real transactions
Parallel runs are recommended if feasible.
7. Go Live and Support: Once confident, cut over to the new ERP:
Freeze Macola data
Train users on the new system
Monitor closely for discrepancies post-launch
Conclusion: Migrating from Macola ERP to a new system is a strategic opportunity that, when executed correctly, can significantly enhance your business operations. By following a structured approach—planning, mapping, transforming, loading, and validating—you can mitigate risk and ensure a smooth transition.
Need help planning or executing your Macola migration? Contact us at Champion Business Solutions for expert ERP migration services tailored to your needs.
Roger Pujol is a business improvement consultant and the founder of Champion Business Solutions, LLC. He speaks and writes about encounters helping small to medium-sized businesses (SMBs) improve their business operations.
© 2025 Champion Business Solutions, LLC
Comments