Merging Two Databases Into a New Database

Hey Guys,

We are looking to merge two separate company databases into 1 new database and start from scratch with Visual. When we originally purchased 6.5.4 they provided implementation guides and checklists that walked you through every field that needed to be populated (even highlighted fields that could not be changed once populated with an asterisk)

Does anyone know if the same type of guide exists for 8.0? Also any tips for anyone who has done this? We want to keep all the data such as customers, employees, parts etc. but want the new database to be a clean start in terms of invoicing, ordering etc.

Find more posts tagged with

VISUAL - Enterprise General Discussions

Comments

unknown

I'm not sure of of mandatory fields for population, but I do have a Data Dictionary for v8 if you would find it beneficial. Not sure if I am permitted to post it here?

Jarrod

unknown

Great. I sent you a request with my contact info. I would greatly appreciate it.

Mike

unknown

HI,

We just recently did an In house reimplementation of Visual 8 from 7.1.2 (only one database though). We did this as we moved to Standard Financials from Global and we were having some problematic data integrity issues. We were also planning on changing our costing method but changed our minds as the tail end of the project. The following are some of the decisions we made and a couple of things to watch out for.

-- We only migrated master data and table data. NO transactional data so no orders, invoices, inventory transactions etc.

- Data that we did migrate went through a complete cleansing review.

- Where we could (and made sense to do so) we imported data through excel imports (The GL Account table was one) this will enforce business rules.(though it can be a slow process and not always feasible)

- We manually re-entered all open transactions after the base files were migrated, this was to ensure data relationships were created correctly.

- Obviously, your aware that there has been some significant changes to the DB from 6.5.4 to 8.0 so make sure you have access to a Data Dictionary. One for 8.0 would be the best but we did ok with one for 7.0 I would not recommend anything less than 7.0

- One of the major changes that you will need to address is the change in 8.0 to using double byte character fields. This has an especially major impact on your binary tables (specifications, notes etc.) You will have to extract the data, convert to double byte and put back into the binary field.

- The double byte fields "nvarchar" also caused a minor issue with our Loftware labeling program. We have odbc fields mapped in some of our labels that were "lost" until Loftware told us about a preference that needed to be set in the application.

By no means is the above all the issues we dealt with but the ones that quickly come to mind.

We were fortunate that we were a single site and relatively close in release levels.

One thing you might want to consider doing (If possible) is applying migration scripts on a copy of your databases to get them to 8.0 Then look at using the migrated database as the foundation for your merge and re-implementation. This would get your data and new tables populated correctly (include the double byte issue).

unknown

So, we are already on 8.0. Just looking to re-implement our database by exporting our static data to the new database. We will not be moving any transactional data, as we will be starting over with the new database. I see how we can export and import GL Account table through Visual, however I am looking for some guidance on exporting and importing the following:

Customer Data

Part Data

Vendor Data

Engineering Masters

0911060553270289.pdf

Copyright © 2025 Infor. All rights reserved.