Migrate from BizAutomation Cloud ERP to Epicor Prophet 21

The BizAutomation GL Chart of Accounts defines the complete account structure across all financial modules and must be imported before any transactional records to satisfy GL referential integrity in Epicor. We export account number, account name, account type (Asset, Liability, Equity, Revenue, Expense), and parent hierarchy. Epicor Kinetic Cloud requires GL Account codes to match the configured fiscal calendar year-start format, so we validate account number length and segment structure against the destination company's fiscal year setup before import. Single-tenant and Data-Mirror configurations may have separate account sets if inter-company structures exist; we export and map each entity's COA separately with inter-company elimination entries flagged for Epicor Multi-Company configuration.

BizAutomation Organization records (customer and company entities) map to Epicor Customer. We extract Organization name, type, billing address, shipping address, payment terms, and credit limit. The Organization ID becomes the Epicor Customer number or an auto-assigned sequential ID depending on the customer's Epicor number format convention. Customer price lists and ship-to addresses export as separate Epicor CustomerShipTo records linked by CustomerID. Multi-site organizations with multiple ship-to locations require one Customer record with multiple CustomerShipTo children.

BizAutomation Contacts map to Epicor Person records linked to the corresponding Customer via CustNum. We extract name, email, phone, job title, and the primary-contact flag. Contact address fields migrate to PersonAddress records if the Epicor implementation uses address-per-contact routing. Custom contact properties (user-defined fields) map to UD fields on the Person table and require field-level review since BizAutomation's proprietary schema stores these in non-standard column structures.

BizAutomation Vendor records map to Epicor Supplier. We export company name, contact information, payment terms, address, and tax ID. Supplier holds before Purchase Orders in the migration sequence to satisfy the VendorRef on PO headers. Epicor Supplier requires a SupplierNum assigned at import; we use the BizAutomation Vendor ID as a pre-lookup key or assign from an Epicor number sequence depending on whether the customer uses supplier-number prefixes for ERP coding conventions.

BizAutomation Inventory Items (SKU, description, cost, price, warehouse location, quantity-on-hand) map to Epicor Part records. Custom item properties and matrix items with variant attribute combinations require field-level mapping because BizAutomation stores matrix parent items and their child variants as separate database rows with attribute definitions embedded in a separate properties table. We reconstruct the Epicor Part with PartUOM, PartWhse, and PartBin records for each warehouse location and quantity snapshot. Standard cost and current cost migrate to PartPlant for each manufacturing or stocking location. Matrix items become a parent Part with PartRev (bill of materials) entries representing the attribute combinations rather than flat child SKU records.

BizAutomation Sales Orders map to Epicor OrderHed (header) and OrderDtl (line) records. We resolve CustomerNum from the Organization mapping, PartNum from the Inventory mapping, and ShipTo address from the Organization's ship-to list. Order date, terms, warehouse, shipping method, and carrier migrate to OrderHed. Line item quantity, unit price, discount, and tax code migrate to OrderDtl. Open orders migrate with their current status; historical closed orders migrate as read-only records with Completed status. Custom order workflow states in BizAutomation map to Epicor OrderHeld or OrderRel records where applicable.

BizAutomation Purchase Orders map to Epicor POHeader and PODetail. We resolve SupplierNum from the Vendor mapping, PartNum from the mapped Inventory Item, and GL Account from the Chart of Accounts for landed-cost and expense PO lines. PO date, terms, and FOB point migrate to POHeader. Line quantity, unit cost, and job number (for MTO POs) migrate to PODetail. Historical closed POs migrate as completed records with the OriginalTaxAmt and TotalAmt preserved for GL reconciliation.

BizAutomation Shipment records map to Epicor ShipHead and ShipDtl. We link each Shipment to the originating Sales Order by OrderNum and OrderLine resolved through the OrderHed mapping. Shipment date, carrier, tracking number, and shipping method migrate to ShipHead. Line-level shipped quantity and back-order quantity migrate to ShipDtl. Epicor requires ShipHead to be posted before inventory transactions are generated in PartTran; we sequence shipment migration after both Order and Inventory records are resident in Epicor.

BizAutomation Projects span the PSA module with tasks, time entries, and contract billing. Project header fields (name, status, start date, end date, project type, owner) map to Epicor Project. Task records map to ProjectPhase and ProjectTask with WBS hierarchy preserved. Time entries and labor bookings map to LaborDtl linked to the project and phase. Contract billing terms migrate to ProjectJob and generate Billing tables in Epicor. Custom project fields and milestone tracking require field-level mapping review since BizAutomation's proprietary schema does not follow a standard project management table structure.

BizAutomation Billable Time Contracts track sold hours against project tasks and activities. Contract type, value, remaining hours, and linked project references map to Epicor Service Contract. Rate schedules and line items with billing rules migrate to ContractDt records. Contracts without a linked project map as standalone Service Contracts with contract-line invoicing controlled by the customer's billing rules. Contracts that reference custom billing logic in BizAutomation are flagged as requiring Epicor BPM configuration post-migration.

BizAutomation Activities (calls, emails, tasks, meetings) on Organizations and Contacts map to Epicor Task records linked via Key1 (the parent record's table and ID). We extract activity type, date, owner, subject, and notes. Task status, priority, and assigned user migrate from BizAutomation's lifecycle stage and owner fields. Custom activity types require mapping to Epicor's task category codes. Activities linked to Persons resolve via the Person mapping; activities linked to Organizations resolve via the Customer mapping before migration.

BizAutomation Opportunities tracking pipeline deals against Organizations map to Epicor Quote (the closest equivalent in Epicor Kinetic since Epicor uses Quote as the pre-sale pipeline record). Stage, amount, probability, close date, and owner migrate to QuoteHed. Line items in the BizAutomation Opportunity map to QuoteDtl with PartNum resolved from the Inventory mapping. Custom pipeline stages in BizAutomation require value mapping to Epicor Quote status codes. Opportunities without a linked Order after close migrate as historical Quote records with a closed status; those with an associated Sales Order are reconciled against the OrderHed mapping.

Orders flowing into BizAutomation from Shopify, BigCommerce, WooCommerce, Magento, or EDI marketplaces carry the same structure as standard Sales Orders and map through the same OrderHed and OrderDtl pathway. We flag the original channel source in a custom field or note field on the Epicor OrderHed since Epicor's native e-commerce connector (Epicor Commerce) replaces the BizAutomation channel integration. The customer's e-commerce team rebuilds the channel connection in Epicor Commerce post-migration, and we document the channel-by-channel order volume so that mapping to Epicor's commerce endpoints is complete.

BizAutomation user-defined properties and custom fields on Organizations, Contacts, Inventory Items, Orders, and Projects do not have a documented schema. We reverse-engineer the column names from the database export and present a field mapping spreadsheet during scoping. Each custom field requires manual review to determine the appropriate Epicor UD table (UD01, UD02, UD05, etc.) and data type (string, int, decimal, checkbox). Matrix item attributes stored as custom properties map to PartRev and PartOpr records in Epicor's manufacturing schema. Custom field migration cannot be automated without customer input on field purpose and acceptable data loss on deprecated properties.