Migrate from Global Shop Solutions ERP to Microsoft Dynamics 365 Business Central

GSS Customer master records split into Microsoft Dynamics 365's party-based model. The GSS Customer (name, address, payment terms, credit limit, 1099 settings) maps to the D365 DirParty and CustTable structures. In Business Central, Customer attaches to Contact records linked to an Account; in Finance/SCM, the Customer account itself serves as the party. We preserve GSS customer ship-to IDs as D365 Delivery Addresses with the correct address purpose. Open AR invoice balances migrate as open customer ledger entries in D365 CustTrans.

GSS Vendor master maps to D365 VendTable with address, contact, and payment term fields preserved. 1099 settings migrate to D365's Tax 1099 flag on the Vendor. Open AP voucher balances and 3-way match status carry forward as open vendor ledger entries in D365 VendTrans. Vendor catalog pricing that exists in GSS maps to Purchase Agreements or Vendor Trade Lines in D365.

GSS Inventory Items with stock levels, cost layers (FIFO/LIFO/average), ABC classifications, and bin locations map to D365 Released Products. On-hand quantities, cost roll-ups, and lead times transfer as inventory on-hand entries across the relevant D365 warehouse sites. GSS bin locations map to D365 warehouse location IDs using the inventory dimension configuration. Average, FIFO, and LIFO costing methods are preserved as the D365 costing version configuration.

GSS BOMs with component items, quantities per assembly, operations routing, work center assignments, and engineering revision control map to D365 BOM and Route structures. Multi-level BOM structures transfer with parent-child relationships intact, and pending Engineering Change Orders (ECOs) carry forward as draft BOM versions. Route operations from GSS map to D365 Production Route operations with work center assignments and cycle times. GSS engineering revision control becomes BOM version management in D365.

GSS Work Orders linked to BOMs and defining the production schedule map to D365 Production Orders. Start and end dates, assigned work centers, labor hour estimates, and completed operations history transfer as production order lines and route journal entries. Actual labor postings from GSS map to D365 route journals so that the production order history reflects the actuals from the shop floor. Back-flushed materials from GSS transfer as inventory issues against the Production Order in D365.

Open and historical GSS Sales Orders map to D365 Sales Orders with line items, pricing, due dates, and fulfillment status preserved. Back-order quantities and partial shipment history carry forward as open order lines. GSS document attachments (order confirmations, specs) migrate as D365 attachments to the Sales Order. In D365 Finance/SCM, Sales Orders create the initial demand that feeds the Master Planning module, which is a capability GSS handles differently; we flag this for the customer's functional team during scoping.

Open GSS Purchase Orders map to D365 Purchase Orders with vendor assignments, line items, expected receipt dates, and landed cost allocations preserved. Received-but-not-invoiced lines carry forward as open receipt lines in D365. GSS landed cost allocations (freight, duty, brokerage) map to D365 Landed Cost vendor and cost allocation rules. Closed POs are archived as completed Purchase Orders for historical reporting.

GSS Chart of Accounts with account numbers, descriptions, account types, and department or cost center distribution flags maps to D365 Main Accounts. GSS department-level GL distributions map to D365 Financial Dimensions, which are configured at the deployment level. We preserve account balances as opening transactions in D365, and GL distribution rules transfer as default dimension templates. Multi-company GSS customers (with inter-company eliminations) receive a separate mapping scope for inter-company account reconciliation.

Open GSS AR invoices, credit memos, and cash receipts migrate to D365 CustTrans open entries with customer payment terms and aging buckets preserved. AR aging reports are rebuilt using D365's Collections Management module with the same aging periods the customer uses in GSS. Historical AR history migrates as posted transactions for collection reporting and audit trail purposes.

Open GSS AP vouchers, invoice images, and 3-way match status carry forward to D365 VendTrans open entries. Vendor payment terms, discount eligibility, and accrued payables map to D365 AP parameters and vendor setup. GSS 3-way match configuration (Purchase Order, Receipt, Invoice) migrates to D365's AP Invoice Approval workflow settings. Invoice images attached to AP vouchers transfer as document attachments to the Vendor Invoice record.

GSS Employee records with demographics, department assignments, pay rates, exempt/non-exempt status, and PTO balances map to D365 Human Resources Worker records. Payroll history and year-to-date earnings transfer as employment history entries for tax and benefit reporting. GSS time tracking data (clock-ins, job assignments, piece rates) migrates as time registrations linked to Production Orders in D365 Manufacturing if the customer licenses the Production module. Note: D365 Human Resources is a separate licensed app from Finance and SCM; we confirm the HR app is in scope during scoping.

GSS inspection results, SPC data points, non-conformance records, and corrective action logs tied to work orders and inventory lots migrate to D365 Quality Management. ISO/AS9100 compliance records carry forward as quality journal entries with references to the production lot. Non-conformance reasons map to D365 quality failure reason codes, and corrective action requests migrate as Quality Orders. This module is only available in D365 Supply Chain Management; Business Central customers use the Quality Management extension or a third-party QMS.

GSS user-defined fields attached to any object (Customer, Item, Work Order) stored as custom properties with specific data types are extracted with their definitions and values. We map them to D365 custom fields (supported in Finance/SCM via the Custom Fields workspace and in Business Central via custom fields on pages). The data type mapping includes GSS text, numeric, date, and checkbox types to their D365 field type equivalents. We flag any custom property that references a GAB-defined screen because those screens do not migrate and the custom field may need a rebuilt page layout in Power Apps.

GSS document attachments stored on transactions, work orders, or the Item master are exported as files with their parent record reference. We map them to D365 attachments on the equivalent record (Sales Order attachment on Sales Order, BOM attachment on BOM). If the customer uses GSS with Box or SharePoint integration, we export the document URLs and remap them to D365's SharePoint integration or Azure Blob Storage depending on the customer's chosen document management strategy in D365.