The most expensive reflex when dealing with faltering software is to replace everything. Usually this is not necessary.
You connect existing systems by first mapping which data is entered twice where, checking whether both packages have a usable API, and then building one connection for the action that occurs most often. Replacing is almost always more expensive than connecting.
STEP BY STEP
This is how you approach it
- Draw out your data flowsWhich data goes from which system to which other, and through whose hands. One A4 is enough and it often immediately makes it clear where the profit lies.
- Highlight where the same data is entered twiceThat is by definition the place where errors occur and where a connection yields the most.
- Check whether both packages have an APISearch for public API documentation. If this exists, then coupling is predictable. If this does not exist, that is the first question to ask your supplier.
- Start with one actionNot the entire landscape in one project. One connection that takes away the daily work, delivers immediate results and teaches you what should be next.
- Build error handling immediatelyQueue, repeat attempts and a notification if something goes wrong. This is the most boring part and the only thing that lets you sleep at night.
- Measure what it yieldedHours per week before and after. Without that number you don't know whether the next link is worth it.
PITFALLS
When replacement is better after all
If a package doesn't have an API and the vendor isn't working on it, you're connecting against a wall. Then replacing it will be cheaper in the long term than continuing to improvise.
Even if a system has not been updated for years or the supplier has stopped, linking is investing in something that disappears.
- No API and no plans — then replacement is cheaper.
- Supplier stopped — don't link to something that disappears.
- Well: start with one action — not the entire landscape.
- Well: error handling immediately — silent data loss is the worst.
- Well: measure — otherwise you don't know if the next one will pay off.
FREQUENTLY ASKED QUESTIONS
More about pairing
Should I move to one system?
Rarely. One system that does everything usually does everything half way. Specialized packages that are well linked work better in practice than an all-rounder.
What if my package doesn't have an API?
Then file exchange is sometimes an interim solution: periodic export and import. That works, but it is slower and breaks more often. We find out in advance what is possible.
How many links do I need?
Usually less than you think. One connection in the place where double entries are made every day often takes away most of the pain.
CONTINUE READING
Of course, continue reading about this subject.
Of double work off?
Tell us which packages you use. We find out what is possible and what it yields.