Migrate from Freedom ERP to Epicor Prophet 21

Freedom ERP Customer records map to Epicor Kinetic Customer with phone, address, and GST details preserved. The Freedom customer code becomes Epicor Kinetic's Customer ID or part of a composite key, and we preserve the GST registration number in the tax registration field. Customer credit limits and payment terms migrate as Epicor Kinetic Customer credit and terms records. We resolve any cross-references from open Sales Orders or Delivery Notes to Customer before import so the Customer record exists prior to any related transactional record.

Freedom ERP Vendor master data maps to Epicor Kinetic Supplier with contact info, payment terms, and tax registration preserved. Vendor-linked PO history and GRN records require Supplier to be imported before PO and receipt records. We map the Freedom vendor code to Epicor Kinetic Supplier ID and preserve any PAN or GSTIN registration in the tax registration fields. Payment terms from Freedom map to Epicor Kinetic terms codes, which may require a lookup table if term labels differ between systems.

Freedom ERP Items (raw materials, intermediates, finished goods) map to Epicor Kinetic Part records with unit of measure, standard cost, and warehouse assignment preserved. The Freedom item code maps to Epicor Kinetic Part Number. We extract Item-UOM conversion factors and map them to Epicor Kinetic's UOMClass and UOM conversions. Stock quantities per warehouse migrate as PartBin records. Item planning parameters (reorder point, safety stock, min/max) map to Epicor Kinetic's planning fields if configured in Freedom.

Freedom ERP BOMs define multi-level product structures with component quantities, scrap rates, phantom assembly flags, and co-product definitions. We extract the full BOM tree from Freedom, reconstruct it as Epicor Kinetic Part BOM records, and map each level to Epicor's BOMRevision and BOMLine structure. Phantom assemblies in Freedom map to Epicor Kinetic phantom BOMs. Scrap rates and operation yield percentages migrate to the respective BOM line fields. This step adds a planning day to the migration scope because BOM correctness directly affects production costing downstream.

Freedom ERP accounts with account type, group, and GST/S-tax mapping migrate to Epicor Kinetic GL Account structure. We export the full COA from Freedom, map account codes and names, and import into Epicor Kinetic's chart of accounts. Cost-center assignments where configured migrate as Epicor Kinetic Department or Cost Center codes. If Freedom uses a different account code length or segment structure than Epicor Kinetic, we flag the segment mismatch and propose a mapping strategy before import.

Outstanding payables and receivables from Freedom ERP include invoice-level detail with due dates, amounts, and GST/S-tax tax breakdown. We export open invoices, match supplier and customer references to the migrated Supplier and Customer records, and create Epicor Kinetic AP and AR open invoice records. GST tax codes from Freedom require a tax code mapping table in Epicor Kinetic before AP/AR import can proceed. Closed historical invoices migrate as AP/AR history records if the scope includes historical financial data.

Freedom ERP Production Orders link to BOMs, work centers, operation sequences, and scheduling dates. We extract work orders with full operation routing, map work center assignments to Epicor Kinetic Resource Groups and Resources, and preserve scheduled start and end dates. The migration maps Freedom production order status to Epicor Kinetic Job status (released, complete, closed). If Freedom uses process manufacturing mode, we assess whether to map to Epicor Kinetic Jobs or Process Jobs based on the destination configuration. Job material requirements (JobMtl) are populated from the linked BOM.

Freedom ERP Employee records include personal details, department, designation, date of joining, and org hierarchy. We export all active and inactive employee records and map to Epicor Kinetic Employee, preserving department assignments and reporting relationships. Employee addresses and contact details migrate as Epicor Kinetic Employee contact information. If Freedom stores employee照片 or documents, we flag these for manual migration to Epicor Kinetic's document management since no export API exists.

Freedom ERP payroll data includes salary components, deductions, payrun history, and earnings per employee. Epicor Kinetic handles payroll through its HRMS module or integration with a dedicated payroll product, not as a core ERP transaction. We export payrun summaries and individual earning records from Freedom ERP as structured historical records, but post-migration payroll setup in Epicor Kinetic HRMS is scoped separately because Epicor's payroll module requires distinct configuration and often a separate implementation phase. We preserve a payroll history export file for the customer's HR team to enter into Epicor Kinetic HRMS or a connected payroll system.

Freedom ERP QC inspection records link to production lots and item batches with inspection results, measured values, and defect logs. We extract inspection records and map them to Epicor Kinetic's QA module where available in the target edition. Custom inspection criteria fields from Freedom map to Epicor Kinetic UDF fields on the inspection record. Not all Epicor Kinetic editions include the full QA/QC module; we verify edition inclusion during scoping and flag any gap as a separate configuration item.

Equipment and machine maintenance logs from Freedom ERP include work orders, spare parts consumed, technician assignments, and labor hours. We export maintenance history and map to Epicor Kinetic's Asset Management module as Asset Downtime and Maintenance records. Linked spare parts migrate as Part transactions against the asset. Technician assignments map to Epicor Kinetic Resource or Employee assignments depending on the destination configuration.

Freedom ERP Project module stores project definitions, milestones, tasks, WBS entries, and resource assignments. We extract project structures and remap them to Epicor Kinetic Project, preserving task dependencies, milestone dates, and billing information. Project accounting and revenue recognition configurations require separate setup in Epicor Kinetic because the financial posting rules differ from Freedom ERP's project accounting model.

Gate entry records from Freedom ERP track inward and outward material movement with vehicle, challan, and material details. We export gate entry logs as structured records and map them to Epicor Kinetic inventory transactions (receipts and shipments) linked to the relevant PO or SO. The vehicle number, challan reference, and material description migrate as transaction-level notes or UDF fields since Epicor Kinetic does not have a native gate-entry object.

Freedom ERP custom fields and non-standard tables added during implementation require manual audit before export. We scan the production database for columns and tables that do not appear in the standard Freedom ERP schema, flag each custom field with its table, column name, and data type, then map to Epicor Kinetic UD fields. Epicor Kinetic UD fields require configuration in the UD Service Designer or via BPM for data population, which adds a schema build phase before data migration. This step is the primary source of migration timeline uncertainty when Freedom ERP has extensive customizations.

Freedom ERP documents stored in the application file store—PDFs, images, scanned files—have no exposed export API. We document all file locations referenced in the Freedom ERP database and provide a file inventory list to the customer for manual upload to Epicor Kinetic Content and Media storage. This is a manual step post-migration and does not migrate as part of the automated data migration scope.