Selling a Used Robot: Plan the Controller Data Handover Before Resetting

A used robot controller may contain more than motion programs. Depending on its configuration, storage can hold production recipes, network settings, logs, user accounts or copies of customer files. Before equipment changes hands, the seller and buyer need an agreed plan for useful operating information and confidential data. Deleting a visible file or restoring a screen to its default appearance is not, by itself, evidence that every storage location has been handled.

Inventory the assets before discussing erasure

Begin with a list of the actual items included in the sale: controller, teach pendant, removable cards, external drives, connected computers and backup copies. Note each component's identity and whether it stays with the machine, remains with the seller or goes to a specialist. The inventory should cover devices used during servicing as well as equipment visible in a listing. Do not post serial numbers, network addresses or account information in a public advertisement.

Ask the equipment owner what kinds of data may be present and which records must be retained. Production programs and calibration information can be valuable to a buyer, but they may also contain confidential process details or licensed material. Distinguish an authorized handover package from the original controller's entire history. A seller should decide what it has the right to transfer before making a copy, rather than assuming that a previous owner's software belongs with the hardware.

Choose a documented sanitization process

The appropriate treatment depends on the information, storage medium, machine design and the owner's obligations. NIST's media sanitization guidance describes a program for making access to target data infeasible for a given level of effort. It is general information-security guidance, not a model-specific instruction for any industrial robot. A qualified administrator and the manufacturer or authorized service provider should determine what operations the actual controller supports and what consequences those operations have.

Some storage may not be user accessible; a factory reset may remove settings needed for commissioning without securely treating every copy of data. Conversely, removing an entire drive may make the system unusable or affect transfer of licensed software. Those possibilities need to be evaluated with the equipment documentation before work begins. Avoid promising a particular erasure result based only on a screenshot of a reset menu.

Separate preservation, transfer and removal

Write three lists. The first contains items the seller must preserve securely, including any records required by its own policy. The second contains the agreed files and documentation that the buyer is permitted to receive. The third identifies data and accounts that should not pass to the buyer. Assign an owner for each list and agree how the recipient will receive authorized files without exposing them through a public listing.

For organizations handling controlled information, NIST's protection requirements discuss sanitizing media before reuse or disposal. Those requirements apply to their stated scope; they do not mean every second-hand robot transaction is subject to the same contractual rules. The relevant privacy, licensing and contractual obligations must be determined for the actual parties and jurisdiction.

Document what was done and what remains

A useful handover record identifies the covered components, the person or organization responsible, the method approved for each medium, when work was performed and how its outcome was checked. It also records exceptions: for example, an inaccessible storage module retained by the seller or a backup that remains subject to the seller's retention policy. Include the controller's resulting functional state and any commissioning steps the buyer will need. Do not put passwords or sensitive files into the certificate itself.

If an external service performs the work, agree on the evidence it will provide and who accepts the result. A certificate or log can help demonstrate that an agreed procedure was followed, but it should not imply that unknown equipment or copies outside the documented scope were covered. If verification is inconclusive, mark the affected item as unresolved and keep it under the seller's control until the owner chooses an appropriate next step.

Plan the buyer's first setup

Before connecting the controller to a production network, the buyer should inventory the received hardware, review its manufacturer documentation and establish new authorized accounts and network settings. Functional checks and safety validation belong to the receiving organization and qualified integrator. Sanitization evidence does not prove the robot is mechanically sound, safely integrated or licensed for every desired application.