…come up with an online field mapping wizard for imports.
How can you call your product "Nimble" with such an antiquated import procedure? Why not a field mapping utility within that recognizes the import headers and gives the user the opportunity to match them with the default Nimble field headers? I've test-driven several web-based CRMs (Salesforce, BaseCRM, Zoho, Close.io, Batchbook and more) and Nimble is surprisingly the first I've used that didn't have a simple field mapping wizard for contact imports.
![](https://secure.gravatar.com/avatar/8ee2e5a067e9d4f415a7f3a3825db463?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
-
Steve commented
I agree this is a serious shortcoming.... Almost every import failed. When designing this permit additional fields to be added on the fly with ability to add data at time of import.