Custom Migration

Overview

If you built your own system (Access, FileMaker, Custom SQL), we can usually migrate it. The key is understanding your schema. We treat this as a collaborative discovery process to map your unique logic to Fulcrum's standard.

Data Extraction Method

Custom Query Extraction or Flat File Export.

  • Review of database relationship diagram (ERD)
  • SQL views to flatten complex data
  • Hands-on mapping sessions

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

  • Hard-coded logic in your old app code won't move; only the data moves.
  • Timelines can vary based on complexity.