Migrate from Logo Go to Microsoft Dynamics 365 Business Central

Logo Go's Chart of Accounts migrates to Business Central G/L Account table. Single-segment accounts map directly to G/L Account numbers. Multi-segment accounts (Department-Cost Center-Natural Account) require a dimension strategy: we either concatenate segments into the G/L Account number or map each segment to a Business Central Dimension (which requires Dimension value setup before account migration). Account type (heading, posting, total) maps to Business Central Account Type with Income/Balance account category mapping for financial reporting.

Logo Go Customer records map to Business Central Customer. The Customer Posting Group maps from Logo Go's customer category code. We preserve Payment Terms and Invoice Disc. Group as Business Central Payment Terms Code and Customer Price Group. Address structure (bill-to, ship-to) migrates to Customer Address and Ship-to Address records. The customer balance (open AR) migrates as a Customer Ledger Entry with remaining amount and due date preserved.

Logo Go Vendor records map to Business Central Vendor. The Vendor Posting Group maps from Logo Go's vendor category code. Payment Terms and Vendor Invoice Disc. Group migrate to Business Central equivalents. Remit-to addresses and ship-to addresses migrate as separate address records. The vendor balance (open AP) migrates as a Vendor Ledger Entry with remaining amount and due date preserved.

Logo Go Items map to Business Central Item records. Item type (inventory vs service) maps from Logo Go's item type flag. Base Unit of Measure and any alternate UOMs migrate as Item Unit of Measure records. Unit Cost and Unit Price migrate as Last Direct Cost and Standard Cost respectively. For manufactured items, we flag the Bill of Materials for Business Central production BOM migration separately during scoping.

Open AR invoices and credit memos from Logo Go migrate as Business Central Customer Ledger Entries with Document Type (Invoice/Credit Memo), Document No., Posting Date, Due Date, Amount (including VAT), and Remaining Amount. Open entries are identified by Logo Go's unpaid invoice flag. We set the Open flag to true so that Business Central's payment application workflow can match payments post-migration.

Open AP invoices and credit memos from Logo Go migrate as Business Central Vendor Ledger Entries with Document Type, Document No., Posting Date, Due Date, Amount (including VAT), and Remaining Amount. Vendor Ledger Entries are created before any payment runs so that outstanding liabilities are visible in Business Central from day one.

Logo Go journal entries migrate to Business Central General Journal Lines. We preserve G/L Account (debit/credit), amount, posting date, document date, and description. Journal batch name is set to a migration-specific batch for separation from live entries. Period integrity is checked against Business Central's fiscal year configuration; entries outside the open fiscal year require year-end close setup before import.

Logo Go Fixed Assets migrate to Business Central Fixed Asset records with acquisition date, acquisition cost, depreciation method, useful life, and accumulated depreciation. Depreciation books (one per depreciation convention) migrate as Fixed Asset Depreciation Book entries. We flag every asset for manual reconciliation against the Logo Go fixed asset sub-ledger because depreciation rounding differences between Logo Go and Business Central's depreciation engine are common.

Open and released Logo Go Purchase Orders migrate to Business Central Purchase Orders with header (vendor, location, currency, payment terms) and line (item number, quantity, unit cost, line discount). Closed and invoiced purchase orders do not migrate as documents; only the AP liability appears in the Vendor Ledger Entry. We flag partially received purchase orders for manual receipt entry alignment in Business Central.

Open and released Logo Go Sales Orders migrate to Business Central Sales Orders with header (customer, ship-to address, currency, payment terms) and line (item number, quantity, unit price, line discount). Partially shipped orders are flagged for receipt alignment. Invoiced orders do not migrate as documents; the AR appears in the Customer Ledger Entry. Completed and cancelled orders do not migrate.

Logo Go custom fields are identified during scoping and recreated in Business Central as AL extension fields or as custom fields in the relevant table. Text custom fields map to Business Central Text[100] or BigText depending on length. Numeric custom fields map to Decimal or Integer. We document every custom field's table of origin, data type, and sample values in the mapping specification. Custom fields with picklist values require a separate Value Mapping document.

Logo Go's localized tax codes (KDV, ÖTV, withholding taxes) map to Business Central Tax Groups and Tax Product Posting Groups. Turkish-specific tax codes require a VAT Posting Setup configuration for each Tax Group. Withholding tax codes migrate as separate Tax Type definitions. We document every Logo Go tax code's rate, type, and posting account in the tax mapping section of the scoping document for the customer's tax advisor to validate against Business Central's regional localization.

Logo Go cost center codes and department segments migrate to Business Central Dimensions. Each Logo Go segment (e.g., Department, Project, Section) becomes a Dimension with its values as Dimension Values. Default Dimensions are set at the G/L Account, Customer, Vendor, and Item level per the customer's dimension strategy agreed during scoping.

Logo Go bank accounts migrate to Business Central Bank Account with bank account number, bank name, SWIFT/BIC, and IBAN. Bank Account Posting Group maps to the reconciliation account. Outstanding checks and deposit-in-transit from Logo Go appear as open Bank Account Ledger Entries in Business Central.

Logo Go inventory transactions (receipts, shipments, adjustments) migrate as Business Central Item Ledger Entries with Entry Type (Purchase, Sale, Adjustment, Transfer), Item No., Quantity, Unit Cost, Location Code, and Posting Date. Quantity and cost are preserved for valuation reporting. We do not migrate closed periods' detailed ledger entries; only open quantities and current average costs are carried forward.

Logo Go users referenced on transactions migrate as Business Central User records resolved by email match. We extract distinct user references from all transaction tables and match against the destination Business Central User list. Any Logo Go user without a matching Business Central User is held in a reconciliation queue for the customer's admin to provision before transaction migration begins.