Each list of records in both tables need a unique value this usually means an ID column in each list. Let’s use the example of multiple contacts linked to a single organisation. That’s because when you import data, such as multiple contacts linked to an organisation, you need to import two sets of information – the contacts list and the organisation list. I need to explain some basic database theory before I can discuss the import process. In this example, it is the Organisation name we will be using on the Contacts spreadsheet. Make sure you have a field which exists on both Contacts and Accounts export spreadsheets. If you get an ID column, then this is useful when linking the tables for the import. In the example we’re using, we want all the Contact fields and all the Organisation fields. These will form columns in your spreadsheet output. In the source system, you’ll need as many fields as possible. If you can only export to CSV, copy and paste the data into a standard spreadsheet format afterwards like XLS or XLSX etc. You can export the data from your source system into a CSV file, but they are usually better suited to the import process. The format of data you want is a spreadsheet. If you have the data in a source CRM or database, you’ll need to get it out in a format which can be manipulated. Map the parent IDs to the importing spreadsheet – this may mean you have to export the parent spreadsheets and use vLookups to get the parent IDs onto the importing spreadsheet first.Įxporting data from your original database Note, the Deals module contains the ID of both the Contact and Account. You’ll need to import three spreadsheets, the Accounts, Contacts and Deals modules. Organisations with contacts and Sales Opportunities You’ll need to import two spreadsheets, one for each. Import data into two modules, the Accounts (Organisation) and the Contacts.

Multiple contacts per organisation or customers You need to import into the Leads module. Non-customers or only one contact per organisation Import parent modules first otherwise, the new records could become orphans. An option is available to match existing records using the IDs, any non-matches and a new record is created. Manually import parent modules first if you’re updating more than one module. Use the migration wizard to import new records into the CRM. Add Parent IDs to Child spreadsheets, use vlookups if required.Split the data into several spreadsheets, one for each module you want to import into.Import from an improvised spreadsheet database or generic list Use the Zoho migration wizard to add the data to the CRM.Optional – Copy and Paste the data into the Zoho import templates you have created.Optional – Export the tables from Zoho’s destination modules, clear the data to create import templates, leave the column headers.Ensure you add Parent IDs to Child spreadsheets, use vlookups if required.Export the tables from the source CRM into a spreadsheet per module, ensure you have the IDs.Before you can do the import, answering the following questions will help you complete your data import.

Zoho creator pulling data from crm