# Preparing an ERP project: use cases and data · DTSC

> An ERP project concerns how the organisation works as much as its software. Scoping must connect intended uses to data, responsibilities and the conditions for going live.

Source: https://www.dtsc.be/en/insights/preparing-an-erp-project/

DTSC

Digital & AI · SPARK

# Prepare an ERP project: uses, data and transition to operation

An ERP project concerns how the organisation works as much as its software. Scoping must connect intended uses to data, responsibilities and the conditions for going live.

27 July 2026 · DTSC · 3 min

Series · 1 of 5

Organise your digital tools

In brief

- Document a few complete journeys: order, delivery, invoicing, procurement.

- Identify the data to be migrated, who is responsible for them and the quality rules.

- Tests must cover roles, interfaces and error situations.

Let’s talk about this topic

## Describe the situations to cover

Document a few complete workflows: order, delivery, invoicing, procurement. Note the variants and exceptions. A commercial demonstration does not replace the verification of these situations with users.

## Prepare the data

Identify the data to be taken over, their owners and the quality rules. Test their migration on a controlled scope before the switch. Document the gaps and correction decisions.

> A feature that is installed is not necessarily usable in your real conditions.

## Test the daily work

Tests must cover roles, interfaces and error situations. Plan for user support, support and acceptance criteria. A feature installed is not necessarily usable in your real conditions.

## Decide on the transition to operation

Define the cutover conditions and fallback solutions with the responsible teams. At DTSC, an ERP implementation is part of LUCID's ICT & Digital, with a duration and deliverable defined at the outset. SPARK can contribute to execution and ongoing support. The scope of your project remains to be specified with the coordinator.

## Prepare usable business acceptance tests

To make testing concrete, start with a complete workflow. Illustrative example: an order is amended after a partial delivery. Users must be able to find delivered quantities, correct what remains to be delivered and check the corresponding invoice. Prepare test data and expected results before the demonstration. Then ask the people who will use the workflow to run it with their usual permissions and the planned interfaces.

- For each scenario: starting point, actions, expected result and approver.

- For each defect: business impact, owner, correction or accepted workaround.

- Before going live: verified data migration, organised support and a tested fallback procedure.

- After launch: a review of incidents and usage with the teams involved.

Written by

The DTSC ecosystem

27 July 2026 · 3 min read

SPARK delivers

## Does this topic concern you?

Let’s start from your situation: a first conversation is enough to see what can be done, with whom and within what timeframe.

Let’s talk about this topic

Explore SPARK

## In the same seriesOrganise your digital tools

Connect workflows, data and responsibilities before changing tools.

[← All publications](https://www.dtsc.be/en/insights/)
