Onboarding — bulk import

Load enterprise architecture data from an Excel workbook: applications, business capabilities, business processes, IT assets, APIs/interfaces, and application–API links.

Who this is for

Enterprise administrators who need to stand up or refresh the portfolio without entering each record by hand. You must be signed in to the tenant.

How to open it

In the workspace, go to Company → Onboarding.

The page title is Onboarding — Bulk Import.

Recommended workflow

1. Download the template.
2. Fill worksheets (or rename your existing sheets to match).
3. Upload the .xlsx file.
4. Confirm column mappings per entity.
5. Fix unmatched rows until every row is matched.
6. Run bulk import.
7. If a run fails partway, resume — completed rows are not duplicated.

Download the template

Choose Download Template on the onboarding page. The file name is PlanIT-Onboarding-Template.xlsx.

Required columns in the template are marked with * in the header. You can also use your own workbook if sheet names and headers are recognizable.

Workbook layout

Each entity type is a worksheet. Sheet names can be the PlanIT table name or a known alias.

Headers are matched to schema column names. Spaces, underscores, hyphens, and a trailing * are ignored when matching. Common aliases such as “Application Name” or “Source Application” are also recognized.

What to put in each sheet

System columns are not imported (Id, audit fields, EnterpriseId, IsDeleted). Fill business fields only.

Applications (Application)

Required: Name.

Typical columns: Description, Domain (also “Business Domain”), ApplicationOwner, ApplicationOwnerEmail, BusinessOwner, BusinessOwnerEmail, ITOwner, SME, CurrentVersion, BuildType, BusinessCategory, LoginMethod, UseageType, Location, OperatingSystem, TechnologyStack, dates (DateInitiated, ProductionDate, GoLiveDate, EndOfSupportDate, and related), user counts, and vulnerability counts.

AnnualCost is optional; the importer can default it.

Business capabilities (BusinessCapability)

Required: Name.

Typical columns: Description, BusinessUnit, BusinessOwner, BusinessClassification, StrategicImportance, TargetMaturityLevel, CapabilityDefinition.

Aliases: “Capability Name”, “Business Capability”.

Business processes (BusinessProcess)

Required: Name.

Typical columns: Description, Type, ProcessDiagramLink, BusinessDomain, ProcessOwner, StrategicGoalAlignment, ProcessStatus, QualityScore.

Alias: “Process Name”.

IT assets (ITAsset)

Required: AssetName.

Typical columns: AssetCode, AssetDescription, AssetType, AssetCategory, Provider, license and support dates, SupportedSystems, SerialReferenceId, DeploymentEnvironment, CriticalityLevel, CostCenter, LifecycleStatus, ContextualNotes, AcquisitionDate.

License and cost counts (NoOfLicenses, InstalledLicenses, AssetCost) are optional.

Aliases include “Asset Name”, “Asset Code”, “Asset Type”.

Dependencies (Dependency)

Required: ApiName.

Typical columns: ApiReferenceUid, DataFlowDirection, ConnectionType, Protocol, TransferFrequency, DataFormat, CriticalityLevel, LifecycleStatus, OwnerContact, Department, FunctionalDescription.

SourceApplicationId and TargetApplicationId are application references. In the spreadsheet, put the application name (not the numeric ID). Headers such as “Source Application” or “From Application” map automatically.

Import applications before dependencies so names resolve. The importer already processes sheets in a safe order (see Import order).

Application links (ApplicationDependency)

Links an application to an API already in the Dependency sheet.

• ApplicationId — application name (aliases: Application Name, App Name)
• APIId — API / interface name (aliases: ApiName, API Name, Interface Name)

Upload and parse

1. Choose Upload & Parse Workbook and select a .xlsx file.
2. PlexArch creates an import session and suggests column mappings from headers.
3. The step indicator moves through Upload → Map Columns → Preview & Validate → Import → Complete.

If a sheet is missing, that entity tab shows “not found.” You can still import the other sheets.

Map columns and preview

Each entity has a tab with:

• Column mapping (one dropdown per PlanIT field)
• Spreadsheet preview with Matched (green) and Unmatched (red) rows
• Per-row issue messages

Save mappings with Save mappings & re-validate. Required fields must be mapped. Application and API reference columns must resolve to names that exist in the workbook or already in the tenant.

Use Re-validate all after you change the file mappings or if you edited data and re-uploaded in a new session.

When you can import

Run bulk import is enabled only when every row across all present sheets is matched (Unmatched count is 0). If rows fail:

• Map the missing required column.
• Fix data types (dates, decimals, integers).
• Use exact application or API names for reference columns.
• Add the missing worksheet and start a new session if needed.

Import order

Rows are written in this order so references resolve:

1. Applications
2. Dependencies
3. Business capabilities
4. Business processes
5. IT assets
6. Application links

Resume and start over

If import fails, pauses, or is interrupted, the page offers Resume import. Already imported rows are skipped (idempotent).

Start Over clears the session and returns you to upload. It does not delete records already committed from a completed run.

After import

Imported records belong to the signed-in enterprise. Review them in the usual inventory screens (applications, capabilities, processes, IT assets, dependency registry).

To add more assets from a CMDB later, use the CMDB Asset Importer instead of this workbook.