Migrate from Furious to Epicor Prophet 21

Furious Client records map directly to Epicor Customer (Customer table). Standard fields (company name, email, billing address, shipping address) migrate 1:1. Furious client-level custom fields map to Epicor UD columns on the Customer table (e.g., Customer_c). Customer payment terms and credit limits require configuration in Epicor's Credit Management module before import if the customer uses credit control. The Customer's short name and region fields in Epicor map from Furious client tags or custom classification fields discovered during scoping.

Furious Projects map to Epicor CS Projects (using the Project Billing module) if Epicor Kinetic is deployed with the CS module, or to Sales Orders if the project lifecycle is order-driven. Furious project status (Active, On Hold, Completed) maps to Epicor Project Phase status values. Project-level custom fields require UD column creation in Epicor's Project Entry before migration. If Epicor DMT (Data Migration Tool) is the ingestion path, projects use the ProjectsCombined DMT template which also generates the WBS root phase. This is the single most complex object mapping in a Furious-to-Epicor migration because Epicor's project structure is hierarchical (Project > WBS Phase > Job) whereas Furious uses a flat project-task model.

Furious Tasks under a Project map to Epicor WBS Phases within the corresponding CS Project. Task assignees map to WBS Phase resources. If the Furious project has a job-production component, the root WBS Phase can trigger Job creation via the CreateJob flag in Epicor DMT ProjectsCombined. Task status (Not Started, In Progress, Complete) maps to Epicor WBS Phase percentage-complete values. Custom fields on Furious Tasks map to UD columns on WBS Phase or Job Operation depending on whether the task represents planning (WBS) or execution (Operation) activity.

Furious Time Entries map to Epicor Labor records linked to the Job or WBS Phase corresponding to the Furious Project-Task combination. The billable/non-billable flag from Furious maps to Labor.LaborType (Productive vs Indirect) or a UD field for reporting segregation. Hours, start time, and end time preserve. DMT Labor upload requires the Job to exist first, making this step dependent on Project migration completing. Epicor's labor entry validation (shift, work group, craft) requires pre-configuration before time entry migration begins.

Furious Quotes map to Epicor Quote Entry. Quote line items migrate as QuoteLine records with part number, quantity, unit price, and discount. The Furious Quote-to-Project linkage requires resolution: if the Furious quote was linked to a project, the corresponding Epicor Quote can be linked to the imported project. Custom fields on Furious Quotes require UD column configuration in Epicor's Quote Entry before migration. Epicor's Quote validity dates and approval workflow need pre-configuration if the customer relies on multi-step quote approval in Furious.

Furious Invoices map to Epicor AR Invoice records. Open invoices are flagged for manual status verification post-migration since payment status can change during the cutover window. Historical paid invoices migrate with full line item detail and payment history preserved. Invoice custom fields map to UD columns on the AR Invoice form. Furious invoice-to-client linkage resolves via the Customer mapping. Note that Epicor's invoice numbering sequence must be configured to accommodate imported invoice numbers if the customer needs to retain original invoice numbers for audit trail continuity.

Furious Purchase Orders map to Epicor PO Header and POLine records. Vendor linkage resolves via the Epicor Supplier records that may need pre-creation before PO migration. PO line items (part number, quantity, unit cost, due date) migrate directly. Furious PO status (Draft, Sent, Received, Closed) maps to Epicor PO status codes. PO approval workflows in Epicor require configuration if the customer's Furious POs went through a multi-step approval process that must be replicated.

Furious User records (name, email, role) map to Epicor Employee records with corresponding User accounts. Furious role strings (e.g., Project Manager, Account Lead) do not map directly to Epicor's permission model; we map to the closest Epicor Security Group and flag any roles requiring manual permission configuration post-import. Inactive users are excluded from migration unless specified. Epicor's employee record includes Department, Shift, and Work Group fields that require pre-configuration in Epicor's HR and Labor modules before user migration.

Furious custom fields on Projects, Quotes, Invoices, and Tasks require field-by-field discovery during scoping, then mapping to Epicor UD column definitions (e.g., Character01, ShortChar01, Number01) with appropriate data types. Epicor UD column setup is done via System Management before data migration begins. Epicor's UD Column Map tool requires a BPM to populate UD fields from other data sources (e.g., ShipTo ZIP into a custom OrderHed field), which is non-obvious and documented in the Epicor User Help Forum. We configure UD columns during the schema phase and validate via Epicor DMT template previews before production load.

Furious binary file attachments linked to projects, quotes, and invoices do not migrate automatically. Epicor's attachment model (document management, external storage links, or SharePoint integration) does not have a direct import path from Furious's file storage. We inventory every Furious record with an attachment and deliver a CSV of attachment references for the customer's admin to manually re-upload post-migration. This is the largest manual post-migration task for most Furious-to-Epicor migrations.

Furious vendors referenced in Purchase Orders map to Epicor Supplier records. Supplier name, address, and payment terms migrate 1:1. If Furious vendors are stored as part of the PO vendor relationship rather than as standalone vendor records, we extract them during discovery and create Supplier records before PO migration to satisfy the POLine.VendorNum foreign key. Supplier-specific custom fields map to UD columns on the Supplier table.

Furious client hierarchy (parent-client with child-client structure) maps to Epicor Customer with the ParentCustNum field set to the parent Customer record. We discover the client hierarchy during scoping, identify the top-level parent for each tree, and set ParentCustNum on each child Customer during import. If Furious uses a tagging or classification system rather than explicit parent-child, we map to Epicor's Customer Group or Region fields for reporting segmentation.