Skip to content

Import Database

Connect your tabular content to myReach so you can save it all in one place.


Integrating a database with myReach enhances your information management by connecting structured data seamlessly.

It unlocks the potential to weave database insights into your broader knowledge network, making it easier to access and use valuable information within your personalised ecosystem.

Steps to Integrate

  1. Go to Profile < Integrations < Import Database

  2. Read the points and click "Continue to import" to see the detailed instructions

  3. Read the instructions carefully

  4. Click "Download Template"

  5. Fill the template with your data as per the instructions provided

  6. Click on "Import CSV" to import your data

  7. If there are any errors, you will see a list of warnings, with the option to see the Formatting rules. Upload the CSV again or igmore the warnings and go to Next step.

  8. By clicking on Next, you have the option to set the Tags, Properties, Comments, Relationships and Relationship names. Fields with warnings will be marked in Orange.

  9. Click on Import Data

The Nodes will be created as per your data in the CSV file.

A separate Workspace is created if you integrate another file.

Properties are created (if they don't already exist) and added in Nodes as provided in the CSV file.

Integration Option

Click on the 3 dots at the top right of the “Import Database" page to see the options.

1. Go to Workspace - Using this option, you can redirect to the specific Workspace that was created with all the imported contacts.

2. Show History Log - Here you can see the Import History of your Import Database integration.

You can see the date when you did the integration along with the number of Nodes created.

3. Remove Integration - Using this option you can Remove the Import Database integration.

The Import Database Workspace will also be deleted and nodes unique to that Workspace will be moved to the “Unassigned nodes” Workspace.


  1. It can seem more complex than other integrations, due to the nature of filling in the fields of the template.