Skip to main content

Migrating from XTRF or Plunet

Migration is done with you during onboarding. This page explains how it works and what we need from you.

How it works​

  1. Discover: we read your system to count clients, vendors, projects and quotes and list the custom fields you use.
  2. Extract: we take a read-only snapshot of a sample of clients and vendors first, then the rest.
  3. Plan: every import starts as a plan listing what will be created, updated or skipped, and any conflicts. Nothing is written until you approve that exact plan; if the data changes in the meantime, the import refuses to run.
  4. Run in parallel: while your old system stays the system of record, we re-sync as often as you like. Only changed records update.

During the parallel run:

  • a record changed in your old system and edited in LanguageOps is flagged for review rather than overwritten;
  • nothing is deleted: rates that disappear get an end date and price profiles are deactivated;
  • each record keeps its original ID, so repeat imports update instead of duplicating.

When LanguageOps prices the same jobs the same way, you freeze changes in the old system, we run a final sync, and you switch.

What comes across first​

Clients and contacts, vendors and language pairs, price profiles and rates (original currency, full precision), CAT grids, minimum charges, payment terms and custom fields. Historical projects, quotes and invoices follow in a later stage and are reconciled against your old system's totals before cutover.

From XTRF​

  • An XTRF administrator creates an integration user and a Home API token, and sends the token to us through a password manager or one-time secret link.
  • Rate cards, CAT grids and payment terms aren't in XTRF's standard API, so your administrator reviews and installs a small, read-only export macro we provide. It calls no update or delete methods.

From Plunet​

  • Either an API user on your Plunet licence (Plunet licenses API access separately), or exports prepared by your Plunet administrator.
  • We start from a sample, map it to the same plan-and-review import, and rehearse it before anything goes live.

Nothing is ever written back to XTRF or Plunet.