acp2md vs acs2md

This page explains the difference between acp2md and acs2md from two angles:

• the engineering view: what each tool does, how it behaves, and where it fits operationally
• the buyer view: why a team would choose one tool, the other, or both together

Both tools convert Atlassian Confluence content into portable Markdown, but they are optimized for different scopes of work.

Compatibility: both acp2md and acs2md support Atlassian Confluence Cloud only.

Safety model: both tools are read-only by design and never modify Confluence content.

Executive summary

acp2md is the focused, page-level tool.

• Best for precise exports, targeted inspections, one-page backup, troubleshooting, migration analysis, and single-document RAG preparation.
• Useful when the team needs to work from a page ID, title, or pasted Confluence URL.
• Well suited to legal, support, compliance, knowledge engineering, and operations teams that often need one exact page rather than an entire space.

acs2md is the bulk, space-level tool.

• Best for full-space backup, continuity copies, disaster recovery archives, large RAG corpora, migration programs, and repeatable synchronization workflows.
• Preserves hierarchy, rewrites internal links, and uses a local state file to download and reconvert only what changed.
• Well suited to platform teams, documentation owners, IT operations, compliance teams, and organizations that need space-wide exports at scale.

If the question is “I need one page or a very targeted operation,” choose acp2md.

If the question is “I need a whole documentation estate or an ongoing synchronization workflow,” choose acs2md.

If the organization needs both targeted precision and bulk operational coverage, use both.

At a glance

Shared capabilities

• Convert Confluence content into clear-text Markdown that customers can own, review, store, and govern.
• Support data sovereignty by moving content into customer-controlled storage and backup systems.
• Help teams prepare content for RAG, search, LLM ingestion, and downstream automation.
• Support Confluence-native retrieval in atlas_doc_format and storage for inspection and troubleshooting.
• Include configuration, licensing, diagnostic, and command-discovery commands such as config, license, doctor, tree, and completion.
• Use read-only GET requests only. Neither tool creates, modifies, or deletes Confluence resources.
• Fit regulated environments where portability, auditability, and retention matter.

acp2md in detail

What acp2md is

acp2md is the single-page specialist.

It converts, retrieves, counts, and inspects one Confluence page at a time. That makes it especially useful when the organization cares about exactness, speed of access, and targeted evidence capture.

What acp2md does well

• Convert one page to Markdown by ID, title, or URL.
• Retrieve one page in native format by ID, title, or URL.
• Count ADF nodes and formatting marks for one page by ID, title, or URL.
• List page properties by ID, title, or URL.
• Refresh a previously exported page efficiently with per-file sync state.

Typical acp2md customer scenarios

• Export a policy page for legal retention.
• Pull a production runbook into Git for controlled review.
• Inspect the raw ADF of a problematic page during migration testing.
• Analyze a single highly formatted page before static publishing.
• Build a small, curated RAG dataset from a shortlist of authoritative pages.

acp2md customer value

• A support engineer can paste a Confluence URL and get the page immediately.
• A compliance analyst can export one high-value page without running a bulk process.
• A knowledge engineer can inspect one page structure before deciding how to chunk or enrich it.
• A program lead can refresh a continuity-critical runbook without re-exporting an entire space.

In short, acp2md is the precise instrument.

acs2md in detail

What acs2md is

acs2md is the documentation-estate tool.

It converts and retrieves Confluence content at space scale, while still exposing page-level commands for teams that want one binary for both targeted and bulk workflows.

What acs2md does well

• Convert an entire space to Markdown by space key or space ID.
• Preserve hierarchy as folders and files.
• Rewrite internal Confluence links into local relative Markdown links.
• Keep a space synchronized efficiently with .convert-sync-state.json.
• List spaces, pages, space properties, and space permissions.
• Support inventory, governance, and access-review workflows at space level.

Typical acs2md customer scenarios

• Maintain a governed continuity copy of a full documentation space.
• Build a disaster recovery archive outside the source platform.
• Prepare a static-site or Git migration for a documentation estate.
• Feed a large RAG or enterprise-search pipeline with a repeatable export.
• Audit access and metadata across a business unit space portfolio.

acs2md customer value

• The team avoids redownloading unchanged content during recurring sync runs.
• The output is structurally usable as documentation, not just a dump of disconnected files.
• Internal links remain navigable after export.
• Space-level properties and permissions support governance, compliance, and security reviews.
• Progress tracking makes long-running jobs safer and easier to monitor.

In short, acs2md is the platform workflow.

Customer decision guide

Choose acp2md when

• You need one page, not a whole space.
• The usual starting point is a page URL pasted from a browser.
• Legal, compliance, support, or engineering teams need targeted exports.
• You want a page-level inspection tool for troubleshooting or migration analysis.
• You want to build or maintain a curated set of high-value Markdown documents.

Choose acs2md when

• You need a full documentation backup or continuity copy.
• You want recurring, changed-only synchronization for a whole space.
• You need portable documentation with preserved hierarchy and rewritten internal links.
• You need inventory and audit capabilities at space level.
• You are planning a large migration, DR archive, or RAG program.

Choose both when

• Operations teams need a bulk platform workflow and support teams still need targeted page actions.
• You want one space-wide export process plus ad hoc page analysis and troubleshooting.
• You are building a managed documentation program with both strategic and tactical use cases.

Buyer perspective

For a technical buyer

acp2md answers the question: “How do we make one page portable, inspectable, and reusable?”

acs2md answers the question: “How do we make a Confluence space operationally portable at scale?”

For a technical evaluator, the distinction is mainly about scope, state management, and output structure.

For a documentation owner

acp2md is ideal for curated, high-signal documents.

acs2md is ideal for estates, taxonomies, and repeatable documentation operations.

For a compliance or governance stakeholder

acp2md is useful for specific evidence pages.

acs2md is more useful for wide-scope reporting, access review preparation, inventory snapshots, and full-space governance exercises.

For an AI or knowledge-platform stakeholder

acp2md is useful for curated, authoritative source documents.

acs2md is useful for broad, repeatable corpora and operational ingestion workflows.

For a security or access-review stakeholder

acp2md helps inspect exact pages and their properties.

acs2md adds the space-level permission and property visibility that matters when reviewing who has access, how a space is governed, and what should be cleaned up before a migration or audit.

Business and commercial positioning

acp2md position

acp2md is the precision export tool.

It is easy to explain to customers who need one of the following outcomes:

• preserve a critical page
• inspect or troubleshoot a page
• analyze a page before migration
• transform a single document into Markdown for downstream use

acs2md position

acs2md is the operational export platform.

It is easy to explain to customers who need one of the following outcomes:

• keep a whole space backed up or synchronized
• prepare for migration or disaster recovery
• build a documentation mirror in Git or object storage
• audit space metadata and permissions
• generate a reusable Markdown corpus for AI and search

Commercial message

• acp2md gives precise control over single high-value documents.
• acs2md gives scalable control over whole documentation domains.
• Both move Confluence knowledge into customer-controlled Markdown, which improves portability, governance, auditability, and reuse.
• Both share the same discovery, diagnostics, and licensing concepts, which reduces training overhead for teams adopting both tools.

Common mistakes to avoid ⚠️

• Do not choose acp2md if the real requirement is ongoing whole-space synchronization.
• Do not choose acs2md if the real requirement is a fast, one-page export for support or compliance.
• Do not frame the decision as “small tool vs serious tool.” Both are serious; they address different operating scopes.
• Do not assume AI use means only one tool. Curated AI sources often start with acp2md, while broad corpora often need acs2md.
• Do not forget that acs2md now includes page-level commands; mixed workflows no longer require switching tools for every targeted inspection.

Buying scenarios 🧩

Scenario: legal or compliance review

Need: selected policy pages, evidence pages, or exact control documents.

Best fit: acp2md

Scenario: continuity or disaster recovery

Need: a current copy of an entire Confluence space outside the source platform.

Best fit: acs2md

Scenario: migration program

Need: inspect a few difficult pages first, then export the full estate.

Best fit: both

Scenario: enterprise AI rollout

Need: create a trusted Markdown corpus for RAG or search.

Best fit: acp2md for curated gold sources, acs2md for broad recurring corpus generation.

Scenario: buyer and customer together

Need: explain the portfolio simply to both a business buyer and the technical team that will operate it.

Best fit: both, with the distinction framed as precision versus scale.

Final recommendation ✅

• Use acp2md when precision is the requirement.
• Use acs2md when scale is the requirement.
• Use both when your Confluence portability strategy needs exact page operations and repeatable full-space workflows.

That is the clearest way to explain the two tools to customers, internal stakeholders, and future buyers.