Switching systems

Move the records.
Keep the meaning.

The difficult part of a change is usually what is already in progress. Start there before discussing a go-live date.

Build a representative sample.

Troctolite does not yet offer an automated Bravo importer or a guaranteed migration service. Begin with redacted exports and an agreed field map. Keep your existing system as the operational record until the replacement has passed your acceptance checks.

  • Customers: stable identifiers, contact fields and the relationships to items and open work.
  • Items: SKU, description, category, weight unit, purity, deductions, cost basis, asking price and location.
  • Stock states: available, held, reserved, sold, in transit and unpurchased intake.
  • Open commitments: repairs, consignment, layaway, offers, loans and customer balances.
  • Evidence: photos, certificates, signed documents and the references that connect them.
  • Money: open tills, deposits, tender totals, unsettled payments and unresolved variances.

Plan the move in stages.

  1. Inventory the source.

    List exports, document stores and integrations. Record which identifiers let records join together.

  2. Map and clean a sample.

    Resolve duplicate SKUs, missing locations, mixed weight units and unclear cost bases before importing anything broadly.

  3. Reconcile the sample.

    Compare item counts, cost totals, open balances and evidence links. Review exceptional records one by one.

  4. Run the acceptance day.

    Price, save, transfer, sell or settle only supported workflows, then reconcile the drawer and permissions.

  5. Agree on the cutover and fallback.

    Choose who signs off, when writes stop in the old system, how final differences are captured and how you revert if the checks fail.

Do not lose the exceptions.

Record to includeQuestion to settle
A ring with a stone deductionAre gross weight, net metal weight and units preserved separately?
An item on holdDoes its restriction survive the move without becoming available?
A transfer already dispatchedWhich shop owns the cost and who is responsible for receipt?
A consigned itemWho owns it, what is owed and is that workflow supported in the destination?
A closed cash session with a varianceCan the explanation and approval be retrieved?
A signed historical documentCan it be found without regenerating it from today’s mutable fields?

Choose a date after proving the fit.

A workflow that is not yet supported cannot be solved by importing its rows into a notes field. Review the availability guide against your open work, jurisdiction and integrations first.

For the first conversation, use redacted examples. Do not send full customer identity records, passwords or payment data through the public walkthrough form. A controlled migration process needs its own agreed data-handling plan.

Bring your own scenario

Let’s work through
your counter.

Tell us what you buy, what you sell and which part of the day needs better software.

Book a walkthrough