S
Simpleasyty
Help Center — Import and export
GETTING STARTED
IntroductionQuick start
CREATE A SCHEMA
Create a schema from a templateCreate a schema from scratch
SCHEMA TEMPLATES
Security Risk RegisterISO 27001 Document ControlSOC 2 Evidence RegisterPolicy ManagementThird-Party RiskData ClassificationApplication PortfolioControlled DocumentArchitecture Decision RecordInformation Asset RegisterBusiness Continuity RegisterGDPR Processing Activity
IMPORT
Import a JSON or YAML schema packageImport Page Properties
FIELD TYPES
Schema field typesText fieldsNumber fieldsYes / No fieldsSingle choice fieldsDate / Time fieldsEmail fieldsURL fieldsConfluence reference fieldsList fieldsField group fields
MANAGE SCHEMAS
Manage schemasIndexed fields and filtersSchema permissions
CAPTURE DATA ON PAGES
Capture metadata on a pageCapture, validate and repair metadata
CREATE REPORTS
Build a Metadata ReportConfigure report filters and viewer controls
STORAGE & PRIVACY
Data residencyStorage in ForgeRetention and deletion
COMPLIANCE
Compliance workflowsMetadata, history and revisions
ADMINISTRATION & TROUBLESHOOTING
Import and exportSchema reconciliation and processesSecurity, storage and limitsTroubleshoot schemas, filters and reports

ADMINISTRATION & TROUBLESHOOTING

Import and export

Move schemas and metadata with Simple Metadata packages.

Export

Schemas, metadata and history can be exported as a Simple Metadata package in JSON or YAML from their respective administrative views.

Import

Package import creates schemas only. If an imported package contains metadata, those values are previewed as ignored; this prevents accidental placement of page-specific data on another site.

Import Page Properties

Open Schemas → Import → Page Properties in the Simple Metadata app. Discover existing Page Properties Reports, or choose a space and label. Review the inferred schema before confirming the import. Each selection creates a new schema and imports matching page data in the background; follow progress in Processes. Original Page Properties macros remain in place. Adding Simple Metadata capture macros is optional and requires permission to edit each page.

Guided schema export

Select the schemas to include, review the export options and download a schemas-only package. Use the metadata and history views for their separate data exports.

What a package contains

Schemas, metadata and metadata history can be exported from their administrative views as a Simple Metadata package in JSON or YAML. Use exports for review, backup of a workflow definition, or controlled transfer between sites.

Import previews the package before it changes anything. It creates schemas only; metadata and history are shown as ignored because they are tied to pages on the source Confluence site.

Move a workflow safely

Import the schema, review its fields, defaults and permissions on the target site, then place new capture macros on target pages. Do not expect a schema import to recreate page-level evidence or macros from the original site.