# Connectors Local to Server (Explicit vs Implicit Mapping) **URL:** \ **Category:** General Q&A\ **Created:** [July 15, 2020, 9:06pm UTC](https://community.easymorph.com/t/connectors-local-to-server-explicit-vs-implicit-mapping/1996 "2020-07-15T21:06:53Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![dgudkov](https://community.easymorph.com/user_avatar/community.easymorph.com/dgudkov/32/5_2.png) [@dgudkov](https://community.easymorph.com/u/dgudkov)\ **Post date:** [July 16, 2020, 4:13pm UTC](https://community.easymorph.com/t/connectors-local-to-server-explicit-vs-implicit-mapping/1996/8 "2020-07-16T16:13:31Z")
> [@adambeltz](#): > > In this scenario it would only be used by EasyMorph. In this case, I would use the native .dset files then. Importing a .dset file, appending data, and writing back can be surprisingly fast even on rather large datasets. Also with files it's easy to create backup copies, if necessary. > [@adambeltz](#): > > Thinking of it as an extension of the EM project itself to store the data efficiently Hot-linking datasets stored in EasyMorph Server is intended exactly for that. The "Import dataset" action can import dataset directly from Server, without creating a local copy. The "Export dataset" action can export directly to Server as well. To get an idea how it can work check out this article: [Server Link explained](https://community.easymorph.com/t/server-link-explained/1878). Note that Server Link is not mandatory for hot-linking. It can be done using regular connectors. In general, you can think of EasyMorph Server as a dataset/file storage instead of SharePoint. EM Desktop has a number of integrations with EM Server which makes it more convenient to use that any other file storage, such as SharePoint. --- _[View the full topic](https://community.easymorph.com/t/connectors-local-to-server-explicit-vs-implicit-mapping/1996)._