---
title: "Export and import data areas"
description: "<p>Planner data files are scoped by area so imports can be identified and validated before mutation."
---

> Documentation Index
> Fetch the complete documentation index at: https://planner.helpcent.re/llms.txt
> Use this file to discover all available pages before exploring further.

# Export and import data areas

<p>Planner data files are scoped by area so imports can be identified and validated before mutation. Do not combine files or rename their internal module IDs.</p>
<h2>Do this</h2>
<ol>
<li>Choose <strong>Export data</strong> and select Notes, Journal, Contacts, Money, Subscriptions, Planner, or Plugins.</li>
<li>Save the generated file without editing it.</li>
<li>On the destination, choose <strong>Import data</strong> and select one to four supported files.</li>
<li>Review the detected areas and conflict policy.</li>
<li>Confirm, then inspect each imported workspace.</li>
</ol>
<h2>Supported boundaries</h2>
<p>Notes exports include task notes because tasks share the Notes authority. Planner exports contain calendar selections, external event state, and planner settings rather than task bodies.</p>
<h2>Batch limits</h2>
<p>A batch accepts a bounded number of files and rejects two files for the same area. This prevents ambiguous precedence.</p>
<h2>Human-readable sharing</h2>
<p>The authoritative data format favors round-trip correctness. For ordinary sharing, use readable note, table, CSV, or report exports when available.</p>
<h2>Good to know</h2>
<ul>
<li>Never import the only copy of a file; preserve the original.</li>
<li>Export current destination data before a large import.</li>
</ul>

Source: https://planner.helpcent.re/sync-data/export-and-import-data-areas/index.mdx
