---
title: "First-use workflow"
description: "When you activate PolyFields on a site that already has ACF options data, a first-use assistant guides you through import or migration before normal language-aware routing begins. ## When the assistant appears When legacy single-language options or *\"ACF Options for…"
url: "https://www.wp-polyfields.com/docs/getting-started/first-use-workflow/"
updated: "2026-06-26"
category: Getting Started
---

# First-use workflow

When you activate PolyFields on a site that already has ACF options data, a first-use assistant guides you through import or migration before normal language-aware routing begins.

## When the assistant appears

When legacy single-language options or *"ACF Options for Polylang"* suffixed values are detected, a first-use assistant appears on ACF options pages. It offers import or migration from the default-language options page.

## Skipping the assistant

Dismissing the assistant (**Skip import** or **Skip migration**) re-enables store routing without running the workflow. Use this only when you are sure existing data does not need to be imported or migrated.

## Background processing

Async import, propagation, and translation jobs use Action Scheduler when available, with WP-Cron as a fallback. Large imports may continue in the background after you start them from the admin.

## Related topics

See [Import from default ACF options](https://www.wp-polyfields.com/docs/import-migration/import-from-default-acf-options/) for bootstrapping from single-language data, or [Migration from](https://www.wp-polyfields.com/docs/import-migration/migration-from-acf-options-for-polylang/)"[ACF Options for Polylang](https://www.wp-polyfields.com/docs/import-migration/migration-from-acf-options-for-polylang/)" if you previously used *ACF Options for Polylang* plugin.