Overview
Migrating from ProShop to Fulcrum focuses on translating ProShop’s highly structured part, routing, and quality data into Fulcrum’s more flexible operational model. Fulcrum preserves the technical fidelity of part definitions and production workflows while simplifying how teams plan, execute, and track work.
Data Extraction Method
ProShop data is typically extracted using structured exports, with approach dependent on deployment:
- On-premise deployment: Structured exports or direct SQL database access
- Cloud-hosted deployment: Standard CSV export utilities
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
- Rich-text fields are converted to plain text during migration
- Some tightly coupled ProShop modules require intentional decoupling during import (e.g. a ProShop custom field might not have a direct equivalent in Fulcrum and could be brought in as a note.)