Support
Notes from the work, not a knowledge base of screenshots.
These are the arguments we make to customers when they ask how something should be done. They are written to be useful to anyone running an integration, whether or not they use ACQI.
I
Articles
10 published · topics: 8
- What a target IT estate review should actually produce Most diligence estate reviews produce a spreadsheet. Here is the shorter list of artefacts that survive contact with the integration programme.
- Designing a discovery credential that survives a security review Read-only is a start, not a design. How to scope, name, time-box and evidence a credential before someone asks.
- Why two inventories of the same estate never agree The disagreements are not errors to be smoothed away. They are the most useful part of the review.
- Plan migration waves by dependency, not by department Departmental waves look tidy on a slide and fail in cut-over. A dependency-first sequence is uglier and survives.
- Rehearse the cut-over against recorded state, not a spreadsheet A rehearsal that reads a plan tests the plan's grammar. A rehearsal that reads the estate tests whether it would have worked.
- Where licence duplication hides after an acquisition Four places the money goes, why the finance view misses them, and what to collect before the renewal date.
- Identity is the first workload you migrate and the last one you finish Why the identity cut-over has no clean end date, and how to plan around that honestly.
- Air-gapped discovery: carrying evidence across the boundary When the target estate cannot reach the internet, the collection model changes. Here is what has to be designed.
- Ten questions to ask before a vendor reads your target's estate A procurement checklist for installed discovery tools, written so that a wrong answer disqualifies rather than merely concerns.
- The 100-day estate journal: what to record after close Integration memory fails faster than anyone expects. A short, disciplined journal is the cheapest control available.