This article explains how to request a full community data export, what’s included, delivery details, and applicable fees.

How to request a full community data export

Let's walk through the three steps you'll take to request a full community data export.

1. Submit a request to Support

Reply to an existing support case or create a new case and state that you are requesting a full export of your community data.

2. Confirm expected content types

While the export contents are predefined by contract, it’s helpful to list the content types you expect to receive, such as:

• Discussions
• Library files
• Blog posts
• Events
• Ideas

This allows our Data Services team to confirm alignment with the standard export scope and address any questions early.

3. Escalation and confirmation

Once received, your request is escalated to the Data Services team.

A team member will follow up to:

• Confirm scope
• Validate eligibility and authorization
• Clarify any technical questions, if needed

TIP: Including your intended use case (e.g., migration or long-term archiving) can help expedite processing.

What’s included in the export

The full export comprises two components:

1. SQL database export (.bak file)

You’ll receive a SQL Server 2019 .bak file containing core community data, including:

• Contact and profile information (demographics, logins, engagement)
• Community memberships and subscriptions
• Discussion posts and comments
• Blogs and blog comments
• Q&A content
• Events and registrations
• Tags, permissions, and related metadata

2. File export (.zip files)

You’ll also receive .zip archives containing files uploaded to:

• Resource Library entries
• Ideas

These files can be cross-referenced using data in the database export.

What’s not included

To set expectations clearly:

• Custom or non-standard content
• Tables or data not listed in the export scope
• Entity Relationship Diagrams (ERDs)
• Custom SQL queries or reports

Export format and tools file formats

• Database: SQL Server 2019 .bak
• Files: .zip archives

How to use the export

The .bak file can be restored using tools such as:

• SQL Server Management Studio (SSMS)
• SQL Server Express (free)

NOTE: CSV exports via API are not part of this service. If you require CSV-formatted data, please contact Support to discuss available alternatives.

Secure delivery

• Export files are delivered via Higher Logic’s Secure File Transfer Protocol (SFTP)
• Files remain available for download for 10 calendar days
• After expiration, files are permanently deleted and cannot be re-enabled

IMPORTANT: Download and back up your export promptly after notification.

Fees & policies

• The First full export is free
• Subsequent Exports:

• Require a new Statement of Work (SOW)
• Standard fee: $500 USD per export
• Each export always includes ALL data and files, not only changes since the previous export

Need assistance?

If you have questions about export scope, format, delivery, or eligibility:

• Contact Higher Logic Support through your open case
• Reference the OC Export Statement of Work signed by your organization

Our team will be happy to help clarify next steps.

SOW document

You can review the attached SOW document to better understand what data is included in the export.