Linnworks to Microsoft Dynamics GP integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between Linnworks and Microsoft Dynamics GP: authenticate both systems, choose the objects to sync (such as Linnworks's Returns & Refunds and Shipping Services), map fields visually, and changes propagate both ways in milliseconds — no code required.

On the Linnworks side: Open Orders, Processed Orders, Stock Items, Stock Levels, plus custom fields where Linnworks exposes them. On the Microsoft Dynamics GP side: Purchase Orders (POP), Inventory Items (IV), GL Accounts & Journal Entries, Receivables & Payables Transactions. Stacksync auto-detects both schemas and converts types between the two systems.

Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.

Common patterns for Linnworks and Microsoft Dynamics GP: Migration in parallel; Shared master data; Split by function. When one system is replacing the other, run both fully live during the transition and cut over without a data freeze.

Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Microsoft Dynamics GP: SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments. Authentication: SQL Server credentials or Windows authentication. Stacksync manages authentication, retries, and rate limits on both sides.

Linnworks: Stock is tracked per location, and channel listings are mapped to internal SKUs, which is the join integrations rely on when reconciling marketplace data. Microsoft Dynamics GP: Microsoft has announced the end of the Dynamics GP product lifecycle, which makes sync-out and migration integrations a common requirement. Stacksync's field mapping accounts for these differences between Linnworks and Microsoft Dynamics GP without custom code.