Hi @DiJohns4,
I completely understand and truly appreciate this tip. My apologies for the continued frustration with the CSV file errors. I’ve connected and shared your helpful feedback with our technical support lead to course correct and inform the agents you’ve corresponded with. We certainly don’t want to compound anymore grief to your experience, man.
You’ve spent too much time doing manual work on this and receiving a notification on when the dev team has fixed the mapper is the way to go (as you’ve signaled that you’re nearly finished). That fix is not visible publicly on our feedback page like most of our features and integrations on the roadmap. You may have already asked a support agent to send you the notification, though if not our support team will be able to do this on your behalf.
You can connect with them here to request the notice be sent to you once it’s ready to go. For anyone else wanting to be contacted when the Easy Crypto mapper is fixed, please reach out and request that notice. 
I want to thank you for the tip again, DiJohns4. It’s very helpful to our teams to know from your perspective, what the ideal resolve would be. Along with our technical support lead viewing this note, we’ll ensure that our dev team is aware to factor in the appropriate changes you’ve mentioned. . Thank you very much for being thoughtful and solutions-based.
Hi, @MangoAggro,
Thank you for highlighting this! We have a few different contacts, though to have a direct email connection to the support team, please reach out here. We’ll also have live chat available for support along with other means of contact here.
I appreciate you both sharing your experiences and ideas for how we can best evolve to have a smoother process importing Easy Crypto CSVs.
Have an awesome day and thank you for shining a light on this! 