Buyer guide

What should a configurator supplier hand over if you leave?

Specify configurator exit deliverables: product data, configuration history, models, documents, interfaces and an agreed transition process.

ConfigurixUpdated 3 min read
Table of contents
  1. What should be on a handover checklist?
  2. How can you test whether an export is useful?
  3. Agree the transition process and timing
  4. Does paying for custom software automatically grant source-code rights?
  5. Is source code the most important handover item?
  6. When should the handover process be tested?

Before buying a configurator, agree what your business can obtain if the supplier relationship ends and whether another team can use it. Product data, saved projects, application code and licensed third-party assets are different items. Their availability and rights of use should be addressed in the agreement.

What should be on a handover checklist?

List the data your business needs and ask about formats, identifiers, history and relationships between records. An image folder is not a product catalogue, and a database backup may require documentation before another team can interpret it.

ItemWhat to clarify
Catalogue and rulesData format, versions, dimensions, dependencies and validation rules
Customer projectsSelected options, configuration versions, status and customer relationships
Quotes and documentsIssued files and references to the correct project version
3D models and materialsAvailable formats and licence terms for each asset
Code and toolsAgreed access and usage rights, dependencies and setup requirements
Integrations and accountsAccount owners, system access, configuration and credential changes

Do not assume an export or source code alone is enough for continued operation. A data dictionary, setup instructions, tests, environment access and product-rule knowledge may also be needed. Specific rights and deliverables depend on the agreement.

How can you test whether an export is useful?

Try a small handover with one product family and a few representative projects. Ask someone outside the implementation team to identify the selected options, units and versions and match an issued quote to its configuration. Record missing definitions and dependencies.

The exercise tests technical usability; it does not decide ownership or licensing rights. Review contractual questions with the people responsible for procurement and legal advice.

Agree the transition process and timing

Define who prepares the export, how sensitive information is transferred securely, how long accounts and environments remain accessible and whether transition assistance is included or separately charged. Review integration accounts, permissions and data-retention responsibilities as well.

The configurator migration guide helps organize records, testing and transition decisions. When discussing a Configurix project, ask which materials, access and assistance are included in the proposed scope and which require separate agreement.

Does paying for custom software automatically grant source-code rights?

Do not assume it does. Ask your advisers to clarify the contract’s treatment of project-specific work, existing software and third-party components or models.

Is source code the most important handover item?

It depends on the transition. A company moving to another system may primarily need product data and project history. A team taking over development may also need agreed code access, dependencies, documentation and environments.

When should the handover process be tested?

Define requirements before signing and agree a suitable time to test an export and its interpretation. This can reveal missing information before an urgent supplier change.

Book a private Configurix demo

Bring your product range, price list and a representative quote. We can define the configuration and sales workflow around your business.

Book a private Configurix demo →

Related articles