Search

Migration plan

Migrate to AWRA OpsHub from spreadsheets.

Migrating off spreadsheets is less about importing files and more about deciding which workbook stops being the source of truth first. We move the highest-risk file into a governed workflow, keep the rest as references, and retire them as trust transfers to AWRA.

SPREADSHEETS AWRA OPSHUB

The plan

A phased move, not a leap.

The same five-phase framework works whatever you are coming from. We start with the highest-risk workflow, prove it in parallel, then expand — so operations never stop while you switch.

01

Audit what you have

Inventory the records, integrations, and workflows in use, and pinpoint the one carrying the most operational risk.

02

Prepare the data

Clean and standardize items, vendors, customers, and locations so they import without carrying drift into AWRA.

03

Configure AWRA

Set up roles, locations, approval paths, and the workflows that mirror how your team actually operates.

04

Pilot in parallel

Move one live workflow and run it alongside the old tool to validate accuracy, approvals, and reporting.

05

Cut over & retire

Make AWRA the source of truth, then phase out the old tool once parity and trust are proven.

What moves

Where your spreadsheets data lands in AWRA.

A practical map of what comes across and what it becomes once it is part of one connected operating system.

From Spreadsheets
In AWRA OpsHub
Item & stock tabs
Item records with locations, movements, and adjustments
Vendor / supplier sheets
Vendor profiles with contacts and terms
Purchase & PO tabs
Procurement requests, RFQs, and purchase orders
Sales & order logs
Sales orders and POS transactions tied to stock
Manual report tabs
Live dashboards that read from workflows

Avoid these

Common pitfalls — and how we de-risk them.

The migrations that go smoothly all avoid the same handful of traps when leaving spreadsheets.

Duplicate item names

Agree one naming standard and de-duplicate before import, or the drift follows you in.

Hidden formulas & owners

Capture the logic each workbook encodes — and who maintains it — before retiring the file.

Big-bang cutover

Move the highest-risk workbook first and keep others as backup until parity is proven.

How long it takes

A realistic timeline.

Most teams retire their first critical workbook in 1–3 weeks, then expand workflow by workflow.

At a glance

Approach
Phased, workflow by workflow
First milestone
Highest-risk workflow live
Operations during switch
Run in parallel — no downtime

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center