Importing and Exporting

Import brings existing content into MemoryCord’s wiki. Export takes captured content back out as a plain file. Both are admin-only (Manage Server).

/import pins

/import pins channel:#support

Seeds the wiki from a channel’s existing pinned messages.

Option	Meaning	Default
channel	Limit the import to one channel	All opted-in text channels

Rules:

• The target channel(s) must already be opted in (/optin). If you name a channel that isn’t opted in, you’re told to opt it in first and nothing is imported.
• Only text channels are scanned this way - forum channels pin per-thread rather than on the forum channel itself, so an opted-in forum channel is skipped by /import pins even if some of its posts are pinned. Seed forum content going forward with the pushpin reaction or /wiki save instead.
• Pins authored by bots are skipped.
• Pins with no text content (an image or file pinned with no caption) are skipped - unlike the live pushpin reaction, import never synthesizes placeholder text for attachment-only messages, since a bulk seed should be real text.
• The reply tells you how many messages were imported, how many channels were processed, and a skip breakdown (bot-authored, empty/attachment-only, inaccessible).

/import history

/import history channel:#support depth:1000 min_reactions:1

Seeds the wiki from messages your community already flagged with reactions, before MemoryCord existed to catch them live.

Option	Meaning	Default	Range
channel	Limit the import to one channel	All opted-in text channels	-
depth	How many recent messages to scan per channel	500	100-2000
min_reactions	Minimum reaction count required to qualify	2	1-20

A message qualifies if it carries either a pushpin or a star reaction with at least min_reactions of that emoji. Star reactions only count retroactively through /import history - there’s no live capture for the star emoji the way there is for the pushpin. If a message has both, whichever emoji has the higher count is used as the stored reaction count.

The same author and content rules apply as everywhere else: bot-authored messages are skipped, messages with no text are skipped, and only opted-in text channels are scanned (forum channels are excluded, same as /import pins). On a smaller server where messages rarely reach the default of 2 reactions, min_reactions:1 catches more.

Idempotency

Both import commands are safe to re-run. Every wiki entry is keyed by its original Discord message, so importing the same message twice never creates a duplicate - the second run just refreshes the stored content and reaction count to match the current message state. This means you can run /import history again after a busy week to pick up newly-flagged older messages without worrying about doubling up anything already captured.

Cooldowns

Each import subcommand has its own five-minute per-server cooldown, tracked separately - running /import pins doesn’t put /import history on cooldown, so a normal onboarding flow of running both back-to-back works fine. Running the same subcommand again inside five minutes gets a “try again in a few minutes” reply.

Both commands can take a little while to finish on a channel with a lot of history, since they’re reading real Discord message data as they go; the bot acknowledges the command immediately and edits in the final summary once the scan completes.

/export

/export channel:#support

Downloads everything captured - wiki entries and Q&A pairs - as a single Markdown file.

Option	Meaning	Default
channel	Limit the export to one channel	The whole server (every opted-in channel)

What’s in the file:

• A title line naming the server and scope, and a generated-at timestamp.
• A Questions & answers section: each pair as a heading with the date, the question text, the answer text, and a source link.
• A Wiki entries section: each entry as a heading with the date, the content, and a source link.
• Nothing else - no full chat history, no messages that weren’t explicitly captured. The export is a view over what’s already in the wiki, not a channel dump.

The export is capped at 500 rows per section (wiki entries and Q&A pairs counted separately), most recent first. If either section is truncated, the file says so explicitly near the top rather than silently dropping older rows.

/export is admin-only and has a five-minute cooldown per server, since building and uploading the file takes real work on a large wiki.

Use cases

• Team or community documentation. Turn your support channel’s collective knowledge into an actual doc you can host, print, or hand to new staff.
• Onboarding. Give new moderators or contributors the export instead of pointing them at a search bar and hoping they find the right threads.
• Feeding an AI assistant. The file is plain Markdown with clear headings and source links - a reasonable format to paste into or upload to an AI tool’s knowledge base, without handing over your whole server history.

Deleting a wiki entry or Q&A pair removes it from future exports the same way it removes it from search - see Saving to the Wiki and Privacy for how deletion works.