Migrate from Logo Go to Epicor Prophet 21

Logo Go's chart of accounts maps to Epicor GL Account (GLAcct table). We preserve account code, description, account type (asset, liability, equity, revenue, expense), and any cost-center segmentation as separate dimension fields in Epicor. Active/inactive status transfers directly. Header accounts and detail accounts in Logo Go map to Summary and Detail flags in Epicor GL Account configuration.

Logo Go Customer records map to Epicor Customer. The Logo Go customer code becomes the Epicor CustID; the customer name and address fields map directly. Credit limit, payment terms, and tax ID transfer as-is. We resolve any Logo Go customer grouping (customer categories, regions) to Epicor Customer Groups configured before import. If Logo Go holds a separate Ship-To address table, these map to Epicor ShipTo records with parent CustNum.

Logo Go Vendor records map to Epicor Supplier. Vendor code becomes Epicor VendorID; vendor name and address fields migrate directly. 1099 flag, payment terms, and tax ID transfer as-is. Logo Go's vendor categories map to Epicor Vendor Groups. Ship-To addresses for vendors map to Epicor SupplierShipTo records if present.

Logo Go Item records map to Epicor Part. The Logo Go item code becomes Epicor PartNum; description, uom, and item type (inventory, non-inventory, service) transfer directly. If Logo Go has a BOM table, those lines map to Epicor PartMtl and PartOpr records for manufacturing items. Stocking uom and stocking location require Epicor Site configuration before Part insert because Site is a required dimension on PartBin.

Logo Go open AP records map to Epicor AP Invoice with a status of Open. Vendor reference, invoice number, invoice date, due date, and outstanding amount transfer as-is. We flag these as carry-forward entries requiring reconciliation to Epicor's AP open balance after migration because Logo Go's aging format does not natively carry forward discount and adjustment line items that Epicor expects on individual invoice records.

Logo Go open AR records map to Epicor AR Invoice with a status of Open. Customer reference, invoice number, invoice date, due date, and outstanding amount transfer as-is. We flag AR carry-forward for reconciliation because Logo Go's payment allocation records may not cleanly map to Epicor's AR Cash Entry process without manual posting.

Logo Go BOM records split into Epicor PartMtl (material components) and PartOpr (routing operations). Each BOM line in Logo Go becomes a PartMtl row with the Logo Go component item mapped to an Epicor PartNum. If Logo Go holds operation sequences and labor codes, those map to PartOpr rows with standard labor and machine hours. BOM revision and effective date transfer to Epicor PartRev.

Logo Go fixed asset records (asset number, description, acquisition date, cost, accumulated depreciation) map to Epicor Equipment records. We flag this as a configuration mapping because Epicor expects Equipment records to be linked to a Site and to a GL Account for depreciation posting. Logo Go's depreciation schedule must be reconciled to Epicor's fiscal year calendar before asset migration; automatic depreciation recalculation in Epicor may produce different balances than Logo Go's final posted amounts.

Logo Go journal entry headers map to Epicor GL Journal Entry records. We extract the journal batch ID, date, source module, and description. Journal lines (account, debit, credit, memo) map to GLJrnLine. We flag this as configuration because Epicor requires the fiscal period to be open before journal entry import, and Logo Go's journal numbering convention may conflict with Epicor's auto-numbering rules that must be disabled or overridden during migration.

Logo Go custom fields do not have a documented API export path; they appear in database exports as additional columns alongside standard tables. We extract them as extra CSV columns and map them to Epicor UD (User-Defined) fields on the equivalent Epicor table (Customer, Supplier, Part, etc.). Epicor's UD field naming convention (ShortChar01, Number01, etc.) requires a configuration step to assign meaningful labels. We document the full custom-field inventory during scoping for manual field creation in Epicor before migration.

Logo Go's localized tax codes (Turkish VAT rates, withholding tables, regional tax overrides) do not have a documented export path. We extract tax codes and rates from database exports as reference tables and map them to Epicor Tax Region and Tax Code records. Customer tax exemptions and vendor tax statuses map to Epicor CustomerTaxRegion and SupplierTaxRegion respectively. We flag tax configuration as a manual-reconcile item because Logo Go's tax jurisdiction structure often includes regulatory overrides that require a tax consultant to reconfigure in Epicor.

Logo Go open sales orders map to Epicor SalesOrder records. Order number, customer PO, order date, and line items (part number, quantity, unit price) transfer directly. Header-level discounts and freight charges map to Epicor OrderHed misc fields. We resolve the Epicor PartNum and CustNum references before insert. Ship-to address and contact map to Epicor ShipTo and CustCnt records. Open orders are prioritized over historical orders because they represent active business that cannot be archived.