Articles in this section

See more

Model Import & Export

Arjun C
  • Updated
Follow

Model Import

Model Import lets you bring an exported model configuration ZIP into TADA as a brand-new environment — creating a fresh Cloud, Model, and Partition pre-populated with all the exported components. Use it to set up a new customer environment, restore a backup, or replicate a configuration across regions.

Table of Contents

  1. Prerequisites
  2. How to Import
  3. What Gets Imported
  4. Import Result

Prerequisites

  • Composer access with Super User permissions.
  • A model export ZIP file — generated from the Export Model feature in Composer.
  • A registered data server in TADA for the target storage provider. The import cannot create a new data server — it must already exist in the system.
  • A unique cloud name — the import always creates a new cloud. If a cloud with the same name already exists, the import will fail.
  • The Deploy tab enabled in your environment configuration.

How to Import

  1. Open Composer and click the Import Model button (upload icon) in the toolbar.
  2. On the Import page, fill in the following fields:
Field Description Required
ZIP File The exported model package (.zip) Yes
Cloud Name Name for the new cloud to be created. Must be unique across the system. Yes
Model Name Name for the new model Yes
Partition Name Name for the new model part / partition Yes
Storage Provider Database type for the new cloud: SQL Server, Oracle, SAP HANA, Snowflake, MySQL, or PostgreSQL Yes
Data Server A pre-registered server matching the selected storage provider Yes
Architecture Name Name for the new architecture. Defaults to the model name if left blank. No
  1. Click Import Configuration.
  2. A progress bar updates phase-by-phase as the import runs. On completion it turns solid green; on failure it turns red.
  3. When complete, you are redirected to the Composer home page with the new environment ready to use.

What Gets Imported

The import processes components in this order:

  1. Creates the Cloud, Model, Model Part, and Model Service
  2. Business architecture (nodes, links, layers, networks)
  3. Model part data and semantic types
  4. Functions, insights, forms, visuals
  5. Master nodes and links, GTM mappings
  6. Data endpoints, backup configs, document extractions, network filters
  7. Finalizes: rebuilds function stores and persisted insight tables

Import Result

On success, the system returns a summary including:

  • Cloud ID and name
  • Model ID and name
  • Partition ID and name
  • Model Service ID and name
  • Architecture ID and name
  • Count of insights and forms imported

Model Export

Model Export lets you package an entire model configuration — architecture, insights, forms, visuals, and more — into a single ZIP file. Use it to back up a model, share a configuration with another team, or prepare for an import into a different environment.

Table of Contents

  1. Prerequisites
  2. What Gets Exported
  3. How to Export
  4. Export Package Format

Prerequisites

  • Composer access. You must have access to the Composer application.
  • Super User or Power User permissions on the model you want to export.
  • The Deploy tab enabled in your environment configuration. If the Export Model button is not visible in the toolbar, contact your administrator.

What Gets Exported

The export packages every component of the selected model configuration:

Component What's included
Architecture Business nodes, links, layers, networks, transactional node mappings
Master Nodes & Links Master node and link definitions
GTM Mappings GTM / transactional data mapping configurations
Insights Insight (view) configurations
Forms Data form definitions
Visuals Visor and widget layout configurations
Data Endpoints API endpoint configurations
Network Filters Network filter definitions
Backup Configs Backup schedule configurations
Document Extractions Document extraction mappings

Not included: Passwords, security tokens, and connection strings are automatically stripped from the export. Actual data records are not exported.

How to Export

  1. Open Composer and select the architecture you want to export.
  2. In the Composer toolbar, click the Export Model button (download icon).
  3. In the dialog that appears, select the application from the dropdown.
  4. Click Export Configuration.
  5. The ZIP file downloads automatically to your browser's default download location.

The file is named: {ModelName}_Export_{YYYYMMDD_HHmmss}.zip

Export Package Format

The ZIP contains a manifest.json at the root and a subfolder for each component type. Large components are split into numbered chunks (chunk_0.json, chunk_1.json, etc., up to 10 MB each). The manifest records the export version, date, exporter user, model name, model part name, cloud name, and source model part ID.

Tips & Notes

  • The export captures a point-in-time snapshot. Re-export after significant changes to keep your backup current.
  • Connection strings and credentials are excluded from the export. After importing into a new environment, reconfigure any data source connections that require credentials.
  • Import is always greenfield. A new Cloud, Model, and Partition are always created. There is no option to merge into an existing model — use the Deployment Pipeline for that.
  • Cloud name must be unique. Choose a name that doesn't already exist in your TADA instance before starting the import.
  • Data server must be pre-registered. Set up the target data server in TADA before running the import — it won't appear in the dropdown otherwise.
  • Large imports take time. The progress bar shows which phase is running. Keep the page open until the import completes.
  • Enrichment mappings (transactional node column-to-property wiring) are included in the export and carry over correctly on import.
  • Insight default filters and column aggregations carry over automatically — no manual reconfiguration needed after import.
  • An includeData option is reserved for a future release that will allow actual data records to be included in the export. It is not yet active.

Related Articles: Deployment — Releases & Pipelines