Configuration Import & Export

Beta

Export and import your community’s configuration as a YAML file.

Overview

Configuration import and export lets you save your community’s setup to a YAML file and restore it later — or apply it to a different community. This is useful for cloning configuration between communities, creating backups, or bulk-setting up tags and fields.

Where to Find It

Go to Settings > Data > Configuration to access the export and import tools.

What Gets Exported

The exported YAML file includes:

• Advocate Tags — name, display name, icon, color, display type, descriptions
• Prospect Tags — name, display name, icon, color, descriptions
• Conversation Tags — name, display name, icon, color, descriptions
• Introduction Tags — name, display name, icon, color, descriptions
• Custom Fields — identifier, label, response type, options, required flag, placement, access settings
• Application Questions — identifier, prompt, response type, options, required flag
• Canned Responses — name, description, slash command, content
• Conversation Close Reasons — name, description (custom only, not system defaults)
• Introduction Close Reasons — name, description (custom only, not system defaults)
• Application Rejection Reasons — name, description (custom only, not system defaults)
• Wallet Configurations — name, currency code, description, unit name
• Social Platforms — platform key, enabled status, display order
• Storefronts — name, primary URL, CTA, domains
• Site Redirects — from path, to path, redirect type, site type, reason
• Waiver Templates — identifier, title, agreement, description, and nested fields
• Message Templates — identifier, content (only customized templates, not defaults)
• Advocate FAQs — question, answer
• Prospect FAQs — question, answer
• Library Items — title, description, URL (text/URL items only, not file attachments)

The export does not include advocate data, conversation history, or other community content — only configuration settings. System-generated close reasons and rejection reasons are excluded since they are automatically created for every community.

Exporting

1. Go to Settings > Data > Configuration
2. Click Export Configuration
3. A .yml file downloads with a name like your-community-config-2026-03-01.yml

The file is a standard YAML document you can open in any text editor.

Importing

1. Go to Settings > Data > Configuration
2. Click Choose File and select a .yml or .yaml file
3. Click Import

The import uses an upsert approach:

• Existing items (matched by name for tags, identifier for fields and questions) are updated with the values from the file
• New items are created
• Items not in the file are left unchanged — nothing is deleted

After import, you’ll see a summary showing how many items were created, updated, or had errors in each section.

Double-check your YAML file before importing. While the import won’t delete existing configuration, it will overwrite matching items with the values from the file.

Use Cases

• Clone configuration between communities — export from one, import into another
• Backup settings before making bulk changes
• Bulk setup — prepare tags, fields, and questions in a YAML file and import them all at once
• Share templates — send a YAML file to another admin to replicate your community’s setup