Migration Guides.

How restaurants should prepare data and workflows before moving existing operations into Limvero.

Migration areas

Migration should focus on clean operational readiness, not blindly importing every legacy field.

Prepare categories, products, SKUs, prices, modifiers, kitchen routing needs, recipes and location-specific differences before import.

Confirm lawful basis, phone/email quality, duplicate handling, loyalty balances, customer groups and consent boundaries.

Prepare warehouses, ingredients, units, opening balances and manual adjustment reasons before enabling writeoff workflows.

Map owners, managers, cashiers, waiters, cooks and service-point roles. Avoid shared POS PINs.

Decide which historical orders, payments, stock movements or reports are needed for reference instead of importing unnecessary volume.

Rotate old credentials, create scoped Limvero API keys, register HTTPS webhooks and validate idempotent consumers.

Use conservative migration controls so data quality issues are found before live restaurant service.

Run migration in a demo or staging tenant before production and compare counts, totals, samples and operational workflows.

Keep the original source export unchanged until the restaurant confirms production data and first-service readiness.

Plan the final cutover around restaurant downtime, staff training, device setup, provider readiness and rollback expectations.

Provider-specific imports and large historical migrations are scoped during onboarding so tenant performance and data quality remain controlled.

Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.