Linbis Legacy sync
Pair this workspace with a Linbis Legacy organization, choose which direction and which records travel, and work the items that are still waiting to be applied.
Linbis Legacy sync (/settings/integrations/legacy) links this workspace to the Linbis Legacy
organization it was migrated from: "Keep this workspace and Linbis Legacy in sync, in both
directions." It exists for the cutover period — while part of your team still works in Legacy and
part has moved here, both sides keep seeing the same shipments, accounts and paperwork.
Only an administrator can reach this page. You get to it from Settings → Integrations.
Connect
Pairing starts in Legacy, not here. Ask a Linbis Legacy admin to click Sync with Linbis 2026 there; Legacy shows them a ten-character code.
- Paste the code into Pairing code. Spaces and dashes are ignored, so
K7M2P 9QZDXandK7M2P9QZDXare the same code. - Choose Check code. This only looks the code up — it does not consume it — and shows you the Legacy organization, the Legacy database and the Environment behind it.
- If that is the right organization, choose Connect.
Read the confirmation before connecting: "You are about to link this workspace to the Legacy organization below. Everything that changes in Legacy will start flowing here."
If the Legacy admin sends you a link instead of a code, opening it lands you straight on the confirmation with the code already checked.
When the code will not connect
| What you see | What it means |
|---|---|
| This workspace has not been migrated from Legacy yet | The data load from Legacy has not run for this workspace. Contact ops before pairing. |
| This workspace was migrated from a different Legacy database | The code belongs to another Legacy database than the one your data came from. Only ops can force this pairing. |
| This workspace is already paired with another Legacy organization | Disconnect the existing pairing first, or use the workspace that belongs to that organization. |
| Already paired with this organization | Not an error. Connecting again replaces the credential and keeps the sync history — this is how you recover after a credential is revoked in Legacy. |
The initial load
The first thing a new connection does is copy the current state of every enabled record type. While that runs the status reads Loading initial data…, with a progress line naming the record type being loaded and the ones already done.
If it stops, the status becomes Initial load failed and a Retry initial load button appears. Retrying is safe: the load resumes where it stopped rather than starting over.
Status
The badge at the top of the connection card is the one thing worth checking daily.
| Status | Meaning |
|---|---|
| Loading initial data… | The first full copy is running. |
| Initial load failed | It stopped part-way. Choose Retry initial load. |
| Syncing | Normal operation — changes flow continuously. |
| Paused | You stopped the flow. Changes made here are retained and travel once you resume. |
| Credential revoked in Legacy | Someone revoked the key on the Legacy side. Ask a Legacy admin to click Sync with Linbis 2026 again and paste the new code here. |
| Catching up (reconciling) | The change window expired and a targeted reconciliation is running. No action needed. |
| Sync stopped: incompatible Legacy service version | The Legacy service is running a version this workspace cannot talk to. Ops is notified automatically. |
| Disconnected | No active pairing. |
Next to the badge the card shows the Legacy database, the change cursor (how far through Legacy's change log each side has read), and counters for waiting items and conflicts.
Direction
Direction decides which side may change the other:
- Legacy → here — Legacy is the system of record; this workspace reflects it. This is the default at pairing and the right setting for most of a migration.
- Both ways — edits travel in both directions.
- Here → Legacy — this workspace is the system of record.
Pick a direction and choose Save; the change is written to the audit log.
Entities
Entities are the record types allowed to travel: accounts, contacts, shipments, quotes, shipping orders, receipts, releases, pickup and delivery orders, AR invoices, AP bills and payments. Switch on only what you want flowing, then Save.
A switch that will not move is one whose record type has not been verified against your Legacy version yet — "Only entities verified against Legacy can be enabled."
If this workspace was loaded from Legacy by the migration tool, ask ops to run the charge-reference backfill before switching on AR invoices, AP bills or payments — without it, invoice and bill lines pile up in Waiting items because they cannot find their charge.
Everyday actions
- Sync now — asks for a cycle immediately instead of waiting for the next scheduled one.
- Pause / Resume — stops and restarts the flow. Nothing is lost while paused.
- Disconnect — stops the sync. "Nothing is deleted: history, conflicts and waiting items are kept. To reconnect later you will need a new pairing code from Legacy."
Waiting items
The Waiting items table lists changes that arrived but could not be applied yet — "They retry on their own or wait for your decision." Each row names the record type, the Legacy id, the reason, how many attempts it has made, and the underlying detail.
Most rows clear themselves: an item waiting on a record that has not arrived yet is applied as soon as it does. For the rest:
- Retry now re-applies one row immediately. Reasons that can never succeed on a retry do not offer the button.
- Retry all re-queues every row in the list.
- Discard drops a row for good. Use it only when you have fixed the record by hand on one side or the other.
A conflict is different from a waiting item: it means both sides changed the same field and Linbis kept the local value rather than overwriting your work. The connection card counts them so they do not go unnoticed.