Q&A

This page answers the questions customers usually ask before they use acs2md in a real bulk-export workflow.

What is acs2md designed for?

acs2md is the bulk space converter in the Climakers Confluence toolset.

Use it when you need to export an entire Atlassian Confluence space into a portable Markdown documentation estate for continuity, migration, retention, compliance, Git-based publishing, or AI ingestion.

If the requirement is limited to one page, acp2md is usually the better fit.

Does acs2md modify Confluence?

No. acs2md is read-only by design.

It does not create, update, delete, or reorganize pages, spaces, properties, or permissions in Confluence. The product reads from Confluence and writes the export to your own environment.

Which Confluence editions are supported?

acs2md supports Atlassian Confluence Cloud only.

It does not support Confluence Server or Confluence Data Center.

What is the difference between sync and incremental mode?

acs2md can keep a local .convert-sync-state.json file in the output directory.

• Incremental mode keeps local files even if the source page disappears later.
• Sync mode can remove local files when the source page has been deleted from Confluence.

This makes recurring exports practical, because the tool can skip unchanged pages and reprocess only the content that actually changed.

When should I choose acs2md instead of acp2md?

Choose acs2md when the unit of work is a full space or a repeatable documentation-estate export.

• You need hierarchy-preserving output for many pages.
• You need a scheduled or repeatable export process.
• You want link rewriting and state-file tracking for a portable documentation set.

Choose acp2md when you only need one page or a narrowly scoped page-level workflow.

Which operating systems are covered by the released binaries?

The current released guidance covers macOS and Linux release artifacts.

Windows release artifacts are not currently documented as published builds in this doc set.

What should I do before my first real bulk run?

Use this order:

1. Install the binary.
2. Create the configuration file.
3. Configure Confluence credentials.
4. Activate the license.
5. Run acs2md doctor.
6. Use space list and space pages to confirm the exact target scope.
7. Run a first controlled export against a known space.

For the detailed walkthrough, see the Installation and First-Time Setup page.

How do I get help if something fails?

Start with the built-in checks:

1. Run acs2md doctor to validate configuration, connectivity, and license state.
2. Reproduce the issue with the smallest safe bulk command you can inspect.
3. Generate a diagnostic bundle with acs2md support.
4. Contact Climakers at support@climakers.com.

The full support workflow is documented on the Support page.

Where should I look next?

• Use Overview if you need the product positioning and business outcomes.
• Use Configuration for config-file structure and credential setup.
• Use Convert Spaces when you are ready to export a space.
• Use List Spaces and List Pages to confirm scope.
• Use Workflows & Recipes for production-style examples.