What should a configurator supplier hand over if you leave?

Before buying a configurator, agree what your company can obtain if the supplier relationship ends and whether another team can use it. Product data, saved projects, software source and third-party assets are different items. Their treatment belongs in the commercial agreement reviewed by your procurement and legal advisers.

Inventory the things your business would need

List catalogue records, rules, material references, price definitions, customer projects, issued documents and relevant operational logs. Identify any model or material asset supplied under a separate licence. Ask for the format, included history and meaning of each export.

A folder of images is not a catalogue export. A database backup may contain useful records but still require application knowledge to interpret. Request a data dictionary and stable identifiers alongside the files your team expects to receive.

Rehearse a small exit while the relationship is healthy

Export one product family and several representative projects. Ask someone outside the implementation team to identify the selected options and match an issued offer to its configuration. Record missing definitions and ambiguous units.

This exercise does not establish legal ownership. It establishes whether a proposed operational handover is usable. Keep the contractual review and the technical test connected without confusing their purposes.

Agree transition responsibilities and timing

Discuss who prepares the export, how confidential information is transferred, how long access remains available and which assistance is chargeable. Include the treatment of integrations and accounts that your company operates. A supplier should not need to guess your retention or customer-access obligations during an urgent transition.

Use the Configurix migration guide to define the records and decisions involved. For a custom project, ask which deliverables are standard to the proposed scope and which require separate agreement.

Does paying for custom development automatically settle source-code rights?

Do not assume that it does. Ask your advisers to confirm the agreement's treatment of bespoke work, pre-existing software and third-party components for the relevant jurisdiction.

Is source code the most important export?

It depends on the transition. A business moving to another product may primarily need product data and project history. A team taking over development also needs a reproducible application and its dependencies.