# Migrating from Chromatic

Bring an existing Storybook workflow across and review the first baseline deliberately.

## Keep your Storybook
Framecheck works with a static Storybook build. Connect the existing repository, generate its CI setup, and upload the same build output you use today. You do not need to rewrite every story.

## Check parameter compatibility
| Existing setting | Framecheck treatment |
| --- | --- |
| `chromatic.disableSnapshot` | Skips capture unless explicitly overridden by `framecheck.skip`. |
| `chromatic.delay` | Capture delay, within the supported range. |
| `chromatic.modes` | Named capture variants. Check viewport and global behaviour. |
| `chromatic.ignoreSelectors` | Ignore selectors when Framecheck-specific selectors are not supplied. |
| `.chromatic-ignore` and `data-chromatic="ignore"` | Ignore-region markers. |

Unsupported provider-specific parameters are reported as warnings. Check those warnings and compare the actual output. Do not assume a configuration key has an effect just because the build succeeds.

## Establish a fresh baseline
Framecheck's accepted images and decisions are separate from your previous provider's. Inspect and accept the first intended results, including browser, font, viewport, and crop differences. This documentation does not describe an automatic import of another provider's baseline history.

## Switch required checks carefully
Run the systems alongside each other while validating the setup if that suits your team. After you have a working Framecheck baseline and policy, update GitHub's required checks deliberately. Remove the old integration and secret when they are no longer used.

## Compare billing units
One story at one viewport in one browser is a visual snapshot. Accessibility adds checks; Smart Snapshots still bills stories checked even when no new capture is needed. Use [billing and usage](/billing/) rather than assuming your old provider's counter maps one-to-one.