Migrating from a legacy integration

Migrating from a legacy integration

Migrating from a legacy integration

On databases that carried a previous 3PL integration, Help > Migrate Legacy Integration backfills the connector and offers Match Orders: it asks the 3PL which of your unbound confirmed orders already exist there and links every match by order reference. Whatever the sweep cannot resolve lands in the Review 3PL Orders table - one row per order at the 3PL, colour-coded by linkage. Pick the Odoo order on a row and press Link to resolve it by hand.

For bulk resolution the review list has a CSV round trip:

  • Export Matching CSV downloads the rows (selected rows, or the whole view when nothing is selected) as a worksheet with the 3PL reference, every reference the 3PL carries, the status, and an Odoo Order column - prefilled where known, blank where not.
  • Fill in the blanks offline - Excel lookups against your order book, or a colleague who knows the history. The Odoo Order column accepts the order number, the customer reference, or the legacy reference.
  • Import Matches uploads the worksheet back. Every row pairing a 3PL Ref with an Odoo order is linked exactly like pressing Link on the row; blank rows are skipped, already-linked rows are never changed, and every problem row (order not found, ambiguous reference, order managed elsewhere) is reported in the result and in a Sync Log entry. Fixing the file and importing again is safe.
    • Related Articles

    • Sprint Logistics adapter - setup and reference

      Everything you need to connect the LataSys 3PL Connector to Sprint Logistics: prerequisites, connection setup, mappings, capabilities and provider-specific behaviour. What this adapter provides Flow Supported Order push and despatch write-back Yes ...
    • ShipHero adapter - setup and reference

      Everything you need to connect the LataSys 3PL Connector to ShipHero: prerequisites, connection setup, mappings, capabilities and provider-specific behaviour. What this adapter provides Flow Supported Order push and despatch write-back Yes Order ...
    • Order behaviour settings

      These settings decide how orders leave Odoo and what happens when reality at the warehouse disagrees with the plan. Each entry covers what the setting does, its default, and a scenario where it matters. The Order Field Mappings section at the end ...
    • Product bindings and SKUs

      How Odoo products become known to the 3PL, the four ways to get them there, what a push actually sends, and how automatic matching links an existing 3PL catalogue without ever creating products behind your back. Product push and enrichment are part ...
    • ShipBob adapter - setup and reference

      Everything you need to connect the LataSys 3PL Connector to ShipBob: prerequisites, connection setup, mappings, capabilities and provider-specific behaviour. ShipBob's Developer API is versioned REST/JSON (this adapter speaks the 2026-07 version). ...