Overview
Our Epicor migration approach focuses on extracting the core manufacturing intelligence — BOMs, Routings, and Inventory — while simplifying the operational data for Fulcrum's modern interface.
Data Extraction Method
Epicor migrations use a SQL-based extraction strategy designed for large, highly customized schemas:
- Full SQL Server database backup (.bak) required
- Targeted extraction from core manufacturing tables
Working from a database backup allows Fulcrum to analyze manufacturing relationships without affecting live production systems.
Commonly Migrated Data
Bills of Materials (Assembly Structure)
Routings / Operations
Items & Assembly Data (Finished Goods, Hardware, Other Purchased Components)
Inventory & Inventory Locations
Customer & Vendors *
Sales Pricing & Current Vendor Pricing
Collaborative Expectations:
Data migration is a partnership. While Fulcrum assists with extracting and formatting the data, we rely on your team’s expertise to translate, clean, and sort through unnecessary data that will clutter the system. Use this as an opportunity to reset and start Fulcrum with clean, accurate data.
* Note: Customer and Vendor exports from Accounting systems typically are preferred as it will be critical that these records match with your customer and vendor data within Fulcrum.
Environments
Sandbox Sites
Available upon request for testing data imports without consequences.
Production Resets
Data entered into your primary Fulcrum site can be wiped or reset as often as needed up until Go-Live. This allows us to iterate and perfect your setup.
Requirements
IT Coordination
Set a plan with your IT team or technical lead to gather this information before your kickoff meeting.
Time Commitment
Please expect this to require at least 2 hours per week from your Data Lead / SME to ensure accuracy during Implementation Phase 2: Build.
