# Migrating from another vendor's macros

If you are moving to Capable Formatting from another formatting app, you do not have to rebuild your pages. A migration wizard converts the macros in place.

Formatting is the largest family in that wizard by a wide margin, because formatting apps ship the most macros.

---

## What converts

* Backgrounds, banners, buttons, cards, LaTeX, tooltips, progress bars and trackers, footnotes and Swagger from several vendors.
* Panels, expands, tabs, dividers, statuses, page trees, activity streams and news, which convert to native Confluence elements rather than to Capable macros.
* Two different vendors' numbered headings implementations.

ℹ️

**Where a native Confluence element does the job, the migration uses that** rather than swapping one vendor's macro for another's. Fewer apps in the stack is a better outcome.

The wizard, the options, and the per-app detail are documented in the [Migration](https://innovator.atlassian.net/wiki/spaces/FMT/pages/1408893720) space.

---

## A few things worth knowing

* Migration writes a new page version, so every change is reversible from page history.
* Some macros from other vendors are detected and reported rather than converted. The migration space lists which.
* Run a pilot space first. It is an hour and it tells you what your own content will do.

---

## Related

[MigrationThe wizard itself.](https://staging.dev.capable-sites.com/wiki/pages/1408893720)

[Neighbouring capabilitiesWhat else ships with us.](https://help.gocapable.com/macros/neighbouring-capabilities.html)

[MacrosWhat things become.](https://help.gocapable.com/macros/macros.html)

---

_Do not rebuild the pages. Convert them._