The most common problem with converting the older versions of ACT! to ACT! by Sage is if there is some damage in the database. Unfortunately, the older versions could become corrupt but not be noticed if you didn’t access that part of the data. As everything needs to be read for a conversion or sync, these functions can show up issues that might have been there for some time.
First, no-matter which version you have, make sure you have a backup of the data before you start.
You should also make sure you have the User Name and Password for someone with Administrator access to the database.
Because the repair tools were improved could fix more types of damage as the versions progressed, I recommend always upgrading earlier databases to ACT! 6.0 and cleaning them there before converting to ACT! by Sage.
If you don’t have ACT! 6.0, you can download the ACT! 6.0 30-day Trial – this will give you the time to convert, clean and repair your database to ready it for converting to the later versions.
Convert Earlier Versions to ACT! 6.0
Always perform a database compress and reindex in the version you have before going to ACT! 6.0. The steps for that conversion depends on how old your version is:
- From ACT! for DOS, see:
Converting an ACT! for DOS Database to ACT! 3.0 or Later Format - From ACT! for Windows/MAC 1.x/2.x, see:
How to Convert an Old ACT! for Windows 1.0/1.1b Database to ACT! 6.0/5.0/2000 Format - From ACT! 3.0 – 5.0 (2000), see:
How Do I Convert a Database Created in a Previous Version of ACT! to a Later Version?
Repair and Clean the ACT! 6.0 Database
Next you should do a repair with ACTDIAG as per:
How To Use The ACT! Data Diagnostic Tool (ACTDIAG) to Scan and Repair a Database
If you already have a later version installed, you’ll need to start ACTDIAG as per:
How to Use the ACT! 6.0 Diagnostic Tool When a Later Edition of ACT! is also Installed
Please note: If you got any red check marks, keep running it till they show all green
But if you’re still getting red checks after 3-4 runs, you’ll need to use additional tools to repair it
or have it professionally repaired
If getting an ACT! Consultant to help you with the conversion (recommended)
I also recommend that they run ABC_Scan on the database
If you are having problems are want to be really sure about your data, I recommend:
Red Flags from Cornerstone Solutions
If it still won’t clean or the conversion below still fails, please contact GL Computing
Centralising Attached Files
If you have attached files, especially if they are stored in different locations or on local workstations on a LAN, you should move these to one folder. You will then need to adjust the links in the database to show the new location. There are a number of tools to do this, I personally use Oak!Check! – Validate Attachments. You can also use it to do any other data cleaning you might need.
Converting to Act! 7.0 – 19.1
You are now ready to install the new Act! as per: Sharing ACT! – Network or Sync (Part 1)
Which ever version of Act! you are converting to, make sure you have the latest build and Hotfix.
See the Act! Download Centre – you might need BOTH a Service Pack and a Hotfix, depending on your install.
Then you should just be able to open the database from ACT! 2010 and it will convert. See:
How to convert an ACT! 3.x, 4.x, 5.x (2000) or 6.x (2004) database to versions 2005 (v7) through v19.1
If you have any questions, please post a comment here or in the LinkedIn Act! Fanatics Group
4 comments:
I'm in real estate and I have a custom field, titled "SQFT". When mapping the fields it does not show, how do I get it to show up?
Depends on where you are talking about...
This is not the best place for technical support. Maybe join the LinkedIN ACT! Fanatics Group as per:
http://www.linkedin.com/groups?gid=49896
And then make sure you post enough information, as per:
http://blog.glcomputing.com.au/2009/05/how-to-get-faster-technical-support-for.html
I'm in real estate and I have a custom field, titled "SQFT". When mapping the fields it does not show, how do I get it to show up?
This is a great post thhanks
Post a Comment