Navigator implementation · Phase 04

Data migration

Prepare the information that needs to move from your existing systems into Navigator, test the migration in advance and make sure legacy records remain available where required.

Accepted formats
Formatted text files or standard CSV
Key dates
Test data and live data submission
Important
Migration does not replace access to your legacy system
Before data is supplied

What your dealership needs to provide

The dealership is responsible for supplying data in a suitable format. Where extraction is difficult, your Project Manager can discuss available guidance or consultancy options.

01

Suitable export files

Provide exported data as formatted text or CSV, with clear field headings and supporting field descriptions where needed.

02

Legacy access

Keep access to your previous system for historic invoices, accounting records and audit information that is not transferred into Navigator.

03

Data quality

Migration is an as-is process. Data is mapped into Navigator but is not automatically cleansed or corrected.

04

Optional assistance

Extraction or data enhancement support may be available separately and should be discussed with your Project Manager.

Data that can be migrated

Common import areas

The exact migration scope is agreed during project planning, but these are the most common areas moved into Navigator.

Parts

Part stock, descriptions, bin locations, retail and cost prices, stock quantities and demand history.

Customer database

Customer contact details, vehicle information and available service history.

Sales Ledger

Account details and open transactions. Imported accounts are renumbered in Navigator.

Purchase Ledger

Account details and open transactions. Imported accounts are renumbered in Navigator.

Migration process

Test first, then move the live data

Two dates are agreed during project planning: one for test data and one for the final live data. Meeting both dates is important to keeping the implementation on schedule.

1

Supply test data

The migration team imports it into a test environment so the structure and mapping can be reviewed.

2

Review the result

Check that the agreed records and fields have been mapped as expected before the live migration.

3

Supply live data

Provide the final export on the agreed date so the live migration can be completed for go-live.

Next phase

Pre-live implementation

With the migration process agreed, attention turns to training, practice and the final preparation before go-live.

Continue to pre-live →