# Import from Obsidian

> Migrate from Obsidian by normalizing your vault structure before import.

Migrate from Obsidian by normalizing your vault structure before import.

For general import docs, see:

- [Import content to Capacities](/reference/import)
- [Bulk Import Reference](/reference/bulk-import)

## Quick migration flow

1. Choose a [type-mapping method](reference/bulk-import#markdown-and-csv-mapping) (folders or YAML `type`).
2. Align notes with Capacities object types and properties.
3. Import connected notes together.
4. Review mapping in Bulk Import, then import.
5. Verify links, properties, and media.

### Warnings

- Choose one primary type-mapping method and apply it consistently
- Do not continue if mapping looks wrong

## Understand the paradigm shift

Obsidian can stay loosely structured; Capacities relies on explicit object typing.

The more consistent your folder/frontmatter conventions are before import, the better your results.

If you want a deeper explanation of this shift, read [Understanding the paradigm shift](/migration/understanding-the-migration-paradigm-shift).

## Normalize type mapping

Use one primary method consistently:

1. **Type folders**: top-level folders like `People`, `Projects`, `Meetings`
2. **YAML type property**: `type` in frontmatter matching target object types

You can mix both, but they should agree.

## Map to object types

Capacities object types are noun-based (`People`, `Projects`, `Books`, `Meetings`).

Group notes into clear noun-based top-level folders first (for example `People`, `Projects`, `Meetings`) or make sure frontmatter `type` values express the same grouping.

Then create matching object types in Capacities before import.

For notes/folders that are not noun-like (`Inbox`, `Templates`, scratch notes), either:

1. Restructure into noun-based groups, or
2. Import as Pages (good for free-form notes, but without properties).

Before import, keep frontmatter and filenames clean:

- Clear, unique titles
- Consistent YAML keys (`title`, `type`, `tags`, `created`, where useful)
- Property names aligned with Capacities names where possible

## Keep connected files together

For better link resolution:

- Import linked notes in the same run
- Keep media paths valid relative to notes
- Avoid splitting tightly linked folders across many runs

## Review mapping, then import

In Capacities, go to **Settings > Import Content**, open the **Obsidian** guide in **Migration guides**, then click **Start importing** and upload your vault or selected folders.

Before importing:

- Confirm recognized object types are correct
- Optionally add an import marker
- Stop and fix structure/frontmatter if preview is wrong

Then click `Analyze`, review, and click `Import`. Keep Capacities open until import completes.

## Verify after import

Check:

- Object type assignment
- Property mapping from YAML/frontmatter
- Internal links and embeds
- Media availability