Overview
Fulcrum helps manufacturers migrate from E2 by translating core quoting, production, and scheduling data into Fulcrum using proven mapping and validation workflows. Whether running legacy Access or SQL-based E2 PRO, our approach focuses on preserving operational intent rather than importing raw tables.
Data Extraction Method
Extraction approach depends on your E2 deployment:
- E2 SQL (E2 PRO)
- Standard SQL Server database backup (.bak)
- E2 Access
- Copy of the .mdb database structure
No downtime required during extraction.
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.
Known Nuances & Watch-Outs
- Fulcrum Shop Setup hierarchy and requirements differ from E2.
- Open and active sales order data can be migrated but will be carefully strategized when planning go-live with your Launch Manager.
- E2 allows free-text entry in many fields which may require cleanup before import.
- Unit of Measure conversions (e.g. 'Each' vs 'Lbs') need strict verification.
- Legacy routing steps often lack precise cycle times.
- Terminology in E2 may differ from what Fulcrum calls something (e.g. ‘Work Centers’ vs ‘Operations’).
- Historical data volume may be selectively limited to reduce noise and improve system performance.