05-07-2010 10:04 AM
Any suggestions/advice/ comments regarding the implementation process itself and/or any insight regarding other business or logistical considerations that may come up as a result of combining databases that previously had different users and purposes would be greatly appreciated.
Please share any tips you may have discovered, especially with regards to managing users access to certain fields or records.
01-16-2013 03:01 PM - edited 01-16-2013 03:04 PM
I've had to do this for some of my clients on occasion. Some thoughts off the top of my head...
Tools like Pat Egan's dup check, Alan Lee's Oak!Merge, MS Excel are very helpful.
edited to add these thoughts:
01-18-2013 12:57 PM
There is documentation in the ACT KB about how to successfully combine multiple databases from a technical perspective.
Also, be ruthless about dropping fields you will not likely use in the final design. Excess "sludge" in the database has significant impact on usability and adoption...