Appearance
Projects
A project is a workspace for a piece of delivery work — an integration or a migration — inside your environment. It gathers, in one place, everything that work involves: the connectors it uses, the reference documents that describe the data, the profiles taken of a source database, the data quality reports on those profiles and on delivered files, and the workflows built to deliver the solution.
Projects are for the delivery team. They don't change how connectors or workflows run — they organise the work around them and keep its context together.
Project types
Every project has a type, chosen when you create it:
| Type | Use it for | What it adds |
|---|---|---|
| Integration | Connecting systems so data flows between them on an ongoing basis | Connectors, reference documents, templates, and workflows |
| Migration | Moving data out of a system, usually once | Everything an Integration project has, plus the Data profile and Data quality tabs for assessing a source before you move it |
Choosing a type
Pick Migration whenever you need to profile a source database and assess whether it's clean enough to move. Pick Integration for ongoing system-to-system delivery. You choose the type at creation — see Create a Project.
Where to find projects
Go to Operate → Projects. The list shows every project in your environment, with its type.
From the list you can:
- Search by name
- Filter by project type — All, Integration, or Migration
- Show archived — include projects that have been archived
Inside a project
Open a project to reach its detail view. A health indicator next to the title reads Healthy or Needs attention, depending on whether the project has any open issues. Four cards across the top summarise its state — Connectors, Workflows, Open issues, and Success rate over the last 7 days — and the work itself is organised into tabs:
| Tab | What it's for | Guide |
|---|---|---|
| Overview | The project's name, description, target, recent runs, and open issues | — |
| Data sources | Link connectors (with a role) and upload reference documents | Link Connectors and Workflows · Add Reference Documents |
| Data profile (Migration only) | Profile a source database — table inventory, completeness, keys, relationship health | Profile a Database |
| Data quality | The project's data quality reports — the connectors profiled from it and the files uploaded to assess: a readiness verdict, findings to triage, the checks each is held to, and functional domains for a connector | Generate a Data Quality Report |
| Templates | Pick the workflow templates the project is built on, and pin a version | Link Connectors and Workflows |
| Plan & implement | Design and build the project's workflows with the project assistant | Plan & Implement |
| Workflows | The workflows delivering this project | Link Connectors and Workflows |
Connector roles
When you link a connector to a project you give it a role, which records what the connector is there to do:
| Role | Meaning |
|---|---|
| Source | The system data comes from |
| Target | The system data goes to |
| Other | A supporting connector that isn't a source or target |
The role is recorded as context for the delivery team and for the AI analysis — it doesn't restrict what the connector can do. See Link Connectors and Workflows.
Health and archiving
A project stays in the list until you archive it. Archive project removes it from the default view without deleting it — archived projects reappear when you turn on Show archived, and Restore project brings one back. See Create a Project.
Related guides
- Create a Project — start a new project and set its type
- Link Connectors and Workflows — connect the systems and workflows the project delivers
- Add Reference Documents — give the analysis business context
- Profile a Database — survey a source database (Migration)
- Generate a Data Quality Report — assess a profiled source or a delivered file
- Plan & Implement — build the project's workflows with the assistant
