Welcome
to the Dynamics help website...
For all your
information needs on Dynamics Nav
[Navision Financials v2, Navision Financials v3,
Navision Attain, Dynamics Nav v4 Dynamics Nav v5, Dynamics Nav 2009
Classic and
RTC]
 |
Summary
This refers
to the conversion of data from legacy systems for loading into Nav
using
Excel
and the Nav dataport functionality. Data loads include master files
(customer,
vendor details for example), configuration files and transactions files
(opening positions).
There are
generally 2 stages to one off data migration process: master file and
transaction file processing.
Master
files
Master
files refer to non transactional data for each module. As an example,
the
master files for Sales and Receivables would be customer details. These
details
would include name, address and contact details. These
details may include
account
numbers if the account numbers are to be retained in
Nav.
Transaction
files
Transaction
files are usually transactions representing a closing position for
loading
into
Nav. In the example given, this would be all open (partly or fully
unpaid or
unsettled) items for customers as at a set date. The data
required for loading
into Navision would typically include account reference,
transaction reference,
description, document and / or due
date, currency code, amount for the currency
code and amount for the ledgers base currency.
The data
migration process presumes that data to be migrated can be provided in
text
or
Excel format and includes conversion of data into a form acceptable to
Navision and data loads using Nav dataports. These dataports
may need to be created as
well!
There
should be no need to manually input any data to be mgrated into
Navision
as
long as the data to be migrated can be provided in text or Excel format.
Process
The data
migration process includes the following stages:
Receipt of
data to be converted.
Data
conversion.
Dataport
development
Data load
test database
Client sign
off
Data load
into live database
For all
data migrations, it is very important to ensure data integrity. All
data
migrations completed by FPC are fully checked against data provided
before
completion and load into the live environment. This presumes
a test and live database exist and that the test database is a
reasonably
current copy of the live database.
Data migration does not refer to any regular data transfers
from, say, legacy systems. |
