Sage Importer Troubleshooting

If you are having problems with the Sage to Tally migration wizard the following should help.  When sending support tickets about the Sage to Tally migration wizard please can you send the "debug.log" file which gets generated after running the wizard, it should be located in the same location as where you run the wizard from.

Error message when running the wizard.

When running the wizard if you receive an error message when either opening the wizard or when its searching your computer to find the data it is likely that the application doesn't have the necessary access rights to run or search the system, this should only occur in windows Vista and Windows 7.

Solution: You need to find a way to run the wizard as a system administrator, the best option is to log on as the local administrator account, the account you use needs to have full access to the file system on your machine and if it doesn't you will receive a number of errors that relate to this issue.

Sage username and password.

Once the wizard locates your data it may ask you for your Sage username and password, you may have never been issued with your username and password and if you are convinced you have never set one up then the following will probably help.

Solution: Sage have advised several users that their username will be "manager" and the password is blank try entering this information into the login box and click Next to see if it accepts it.  Unless you use Sage on a network configuration with security in place it is probably the case the above will be correct.  This help article may give you more information:

Locating Sage data file.

The primary function of the Sage to Tally wizard is locating the data of your Sage application by locating a file with the name "COMPANY" with no file extension.  If you are running the wizard and it cannot locate the data it will display an error message to this effect and should give you the option to browse to the Sage directory.

Solution: According to some users the company file can be located by opening Sage going to the "Help" menu and selecting "About" option.  It should give you an idea where the file is located which should help you browse to this location in the wizard to locate the file.  You can try browsing to the suggested directories to find the default location of the company file: Windows XP: C:Documents and SettingsAll UsersApplication DataSageAccounts(YEAR) C:Documents and Settings(YOUR NAME)Application DataSageAccounts(YEAR)

Windows Vista/7 C:UsersAll UsersApplication DataSageAccounts(YEAR) C:Users(YOUR NAME)Application DataSageAccounts(YEAR)

As a last resort you can try searching your system for the file yourself by using Windows search to do a full search of your system.  If you go to the "Start" menu in windows and click on Search or use the desktop search option if you have that installed, alternatively go to My Computer and click on the search button (Ctrl+E).  You should be looking at a search window and have options down the left to tweak your search, the most important options are the "Search system folders" and "Search hidden files and folders".  Run the search for the "COMPANY" file and then try locating the sage directories listed in the results in the wizard and see if that works.

Wizard not pulling in all my data.

Sometimes the wizard will not pull over all the data from the Sage application maybe it only imports all of your data up to a certain date.

Solution: The cause of this usually relates to the data not being committed in sage.  The wizard will only import data from Sage which has been committed, never having used Sage we cannot advise how you do this.  Once you commit the data in sage try running the import process again and it should import the remaining data into Tally.

Conversion failed when converting the nvarchar value '4/' to data type int.

If you get an error like this after starting your import, it is because the wizard has extracted your data in US date format (mm/dd/yyyy).  The wizard only supports UK date format (dd/mm/yyyy).

Solution: Change your regional settings in the Windows control panel to UK.  Re-run the wizard.  Don't forget to change back to US Settings when you're done.

Back to Knowledge Base