Onboard an existing landscape
Turn an existing inventory and its supporting documents into a model your team can check and use.
On this page
Agree on the first useful result
Choose a question that gives the work a boundary. A fictional distributor wants to understand which applications support order fulfilment before replacing its warehouse system.
Write down the business area, the decision owner and the records needed to answer the question. Agree who can confirm the application list, integrations and business context.
Prepare the material
Keep the original material available while you review the model.
| Material | What to establish |
|---|---|
| Application inventory | Consistent names, purpose and ownership |
| Integration documentation | Sending application, receiving application and business data |
| Business process or capability map | The business work that applications support |
| Roadmap or decision record | Intended changes, affected records and reasons |
Separate facts, estimates and open questions. Two rows with similar names may represent one application, separate deployments or different products. Resolve the identity before combining them.
Bring in a small sample
- Confirm the intended workspace and your access.
- Search for existing records so the sample reuses what Atlas already contains.
- Follow the import guide for the supported entry path. Use AI-assisted drafting when your connection supports it.
- Check the sample with a responsible owner before extending the approach to the remaining material.
Connect and verify
For the warehouse example, establish which application sends an order, which receives it and which data object represents it. Attach the source used to check that account. Review the result from both ends of each important integration, then ask an owner to walk through one real business scenario using the model.
Decide whether the result is ready
- The important applications have distinct identities and a known source.
- Critical integrations have confirmed endpoints and direction.
- The model connects to the relevant capability or process.
- Open questions have someone responsible for resolving them.
- The decision owner understands the model’s coverage and remaining gaps.
If imported records look incomplete, compare the accepted input with what reached the workspace before repeating the import. Use Validate changes and review model quality for the next review.