An unnamed ERP migration knowledge concept
This concept has no name, no domain and no code. The title above describes it rather than naming it, because naming a concept is the first step towards describing it as a product.
A research question about whether organisations could share tested ERP migration patterns with each other without sharing anything about their customers. There is no name, no domain, no prototype and no code.
Last verified
The question
Could a neutral, secured library hold anonymised ERP migration patterns that several companies contribute to and reuse, while customer-specific information stays private?
What thinking there has been
- The interesting part is not storage but incentive: a contributor has to get something back that is worth more than the effort of anonymising and publishing a pattern.
- Versioned public mapping rules and contractual portability are the two threads that seem most worth pulling if this is ever explored further.
Limitations
What this is not, stated as plainly as possible.
- Nothing has been built. There is no prototype, no repository, no deployment and no validated business adoption.
- It has no name. The heading above is a description, not a product name.
- No organisation has agreed to contribute anything, so the central assumption is entirely untested.
Evidence
There is none, because nothing has been built. That is the honest state of this concept, and it is why it appears here rather than in the network.