urgent help needed

vikas

hi...

wht is the proces of migrating data from 2.6 to 3.7

please help ASAP...

Tommy_Schou

The process is quite simple. Read the documentation for it! :twisted:

Unfortunately it can be quite a drag to upgrade to 3.70. You really should read through the documentation for the upgrade toolkit which you can find on the 3.70 product CD.

vikas

i just want to know how to migrate data from 2.6 to 3.7.

i have already done with objects......

Tommy_Schou

If you have already upgraded your objects then you have undoubtedly also stumpled upon the documentation for upgrading data...

The two main problems with data are concerning dimensions and the new Det. Ledger entry-tables that exist in 3.70. There are procedures and conversion tools for both in the upgrade toolkit folder on the product CD.

Did you re-code all the customizations in v3.70 or did you port the objects?

Luc_VanDyck

As Tommy said ( in his message dated 11 May 2004 15:38 ), it's in the docs. No use to copy all the info here, right?
It's a matter of importing fobs and running the upgrade codeunits in the right order.

vikas

Thanks. But i want to know while taking up the backup from the older db do i need to take the entire backup/just the objects/just the data. (This is for data migration)

Also, please let me know the process of restoring it back in 3.70.

Thanks in advance

Luc_VanDyck

You need a backup of everything (objects and data), because you are overwriting the objects with the new versions.

And as said before ... it's in the docs.

6.1 UPGRADING THE DATABASE

The next step in the upgrade procedure involves upgrading the customer’s database to Microsoft Business Solutions–Navision 3.70. The first step is to restore the backup of the customer’s database that was made earlier.

To restore the database:
1 Create a new database in Navision 3.70.
Make the database large enough so that you can carry out the rest of the steps. You can always reduce the size of the database later when you know the required database size. You can reduce the size of the database by making a backup of the database, creating a new smaller database and restoring the backup into this new database. We recommend that you set the new database to twice the size of the old Navision database.
2 Restore the backup of the customer’s old database that was saved as data.fbk into this new database. This is the backup that you made in step 3 on page 7.

This can be read in step 3 on page 7:
3 Make a backup of the customer’s Navision Financials database after you have implemented the new object names and call it, for example, data.fbk.

jfl

Problem is that good old Microsoft upgrade toolkit is pants. We are currently upgrading a client and after 2 weeks of pissing against the wind Microsoft GB owned up and told us that the upgrade toolkit has never worked. But there is hope, Microsoft have a patch which they will only tell you about if you actualy phone them and kick up a fuss. Don't know if problem is unique to GB but it might be a place for you to start.

What the other people are telling you is basically correct, that it is just doing things in the correct order, but if your DB is bespoked you require the toolkit.

Like us you may be getting problems with tables which don't actualy exist.
The GB migration tool also only creates a 4 field customer table.

vikas

can u tell me in detail....so tht i can ask them about this tool kit.