TMS next to your existing system

Quanty can work in two ways:

Next to your existing TMS (a parallel run): Quanty copies the data from the system you already use, so your team can work in both at once while you move over at your own pace.
On its own: Quanty is your TMS. You start from your own data, or from what was copied before.

You can also bring your history in from files at any time, with or without a connection (see Bringing data in from files).

A connection to your existing TMS

The connection is set up by Quanty's team: they enter the access details your existing system provides, and they are the ones who switch it on, off, or to Quanty on its own. Your organization sees the connection in TMS settings, Connections, read-only:

whether it works, when the last fetch was and how many records were copied;
a problem in plain words, if there is one: your existing system does not let Quanty in, its licence has run out, or it does not answer;
Fetch now (admins), to fetch straight away instead of waiting for the next scheduled fetch;
Differences: N, which opens the list of differences (below).

What is copied: contractors and their contact persons, vehicles, drivers, orders (with their places, loads, labels, contacts and owner), invoices, costs, pallet entries and documents. Orders still on the road are read again more often, so their progress stays current. Orders whose owner in your existing system is matched to a member of your team land in that person's My work.

During the parallel run

"Parallel run: your existing TMS is the main system; Quanty writes to nobody about these records."

Copied records carry an origin mark: "Comes from …, where its number is …".
Quanty sends no reminders, e-mails, WhatsApp messages or requests for documents about copied records, and never puts a copied invoice into KSeF: that system already does it. The assistant in chat lists such records as left out, and the pallet and document reminders say why they were not sent.
What you create in Quanty yourself is yours as usual.
A cost copied from your existing system shows who approved it there and when, and that is never taken as an approval in Quanty. A contractor's accounting account (konto FK) is copied and can be edited.
When your existing system says a tractor runs with another trailer or driver than Quanty's fleet register, a set proposal waits for a person (see Switching a set).

Differences

Differences shows where Quanty says something else than your existing system. Quanty keeps your value until you decide. Filter by Kind of record (orders, contractors, contact persons, vehicles, drivers, invoices, costs, pallets), and for each difference:

Keep the Quanty value, or Take from your existing system.
A record deleted in your existing system is never deleted by Quanty: Keep in Quanty, Cancel in Quanty (for an order; an invoiced order is corrected on its invoice first) or Archive.
When a copied invoice names a freight the order does not have: Enter the freight from the invoice or Leave as it is.

A route, goods or lines that differ cannot be taken over in one click; open the record and correct it there.

Quanty on its own

When your team is ready, Quanty's team switches the connection to Quanty works alone:

Quanty stops fetching. The access details stay, so the step can be reversed.
Everything copied stays in Quanty, and the copied records keep their origin mark, dimmed.
Reminders and e-mails for new work are sent by Quanty from then on. Finished history copied from the old system stays quiet.
Differences still compare with what was fetched last.

Switching back on reads everything once more from the start. Ending a connection for good leaves everything that was copied in Quanty.

Test data for a parallel run

For a demo or a test, Quanty's team can fill an organization with sample data in the shape of an existing TMS. It is clearly marked, nobody receives messages about it, and it is removed in one step.

Bringing data in from files

Without any connection, the registers read your own files:

Orders: Import from a file (Excel, CSV), one order per row; orders already in Quanty are skipped. The orders report of a supported existing TMS can be read as it is. See TMS orders and quotes.
Contractors: Import from file (CSV or Excel, one contractor per row) on the contractor register. Contractors are matched by NIP, or without a NIP by the exact full name, and nothing typed in Quanty is overwritten: only empty fields are filled.
Pallets: Import your old pallet calendar (.xlsx or .ods), and Compare with the sheet to check the balances against it. See TMS pallets.
Absences and equipment: lists exported from a supported existing TMS, read on the People and Workshop pages. Ask Quanty's team whether yours is supported.
Fuel: card transaction files from your fuel card suppliers. See Fuel.
KSeF: purchase invoices become carrier costs, and your sales register can be read too. See KSeF e-invoices.