AugForums.com

An Acumatica User Group

  • Free
    • Start Here
    • In-Person Gatherings
    • Power BI Workshop
    • Podcast
    • Rolodex
    • Blog
    • Forums
  • Paid
    • AugSQL
    • GI Course
    • GI Library
    • Consulting
  • Register

Importing New Customers by Email Address in Acumatica

October 18, 2016 by Tim Rodman

You might want to import new customers from an eCommerce site into Acumatica, but you don’t want to import them if the email address already exists.

This post is a bit off topic, but someone asked about it recently so I thought I’d cover it here.

Maybe you get orders in to your eCommerce site, but before importing them you need to create the customers.

Let’s assume that you are auto numbering your Customer IDs so the Auto Number checkbox is checked on the Segmented Keys (CS202000) screen in Acumatica like this:

2016-10-21-16-43-07

Let’s also assume that you are using the customer’s email address as the unique identifier for the customer. This wouldn’t work very well in a business to business situation because every person at a company would get a new customer created when they should probably all be contacts under the same customer. But this should work fine in more of a retail situation where each unique email address is assumed to be a completely separate customer.

I made a really simple Excel import spreadsheet to demonstrate this concept:

2016-10-21-16-46-55

Then I attached the spreadsheet to a Data Provider in the Data Providers (SM206015) screen and then created an import scenario in the Import Scenarios (SM206025) screen that utilizes the Data Provider.

My Import Scenario looks like this:

2016-10-21-16-46-56

This is a very simple example, but hopefully it illustrates the point.

A few things to note about the screenshot above:

  • The second row is what tells it to lookup by email. Notice that I’m not feeding it Customer ID anywhere because the Customer ID will automatically get created by auto numbering.
  • When this import scenario runs, it will update the customer if it finds one with a matching email. If it does not find a matching email, then it will create a new customer with the Customer Name and Email from the import file (lines 3 and 4 above). You can add additional fields to the import so it will update/create those fields as well.

So that’s it, pretty simple.

 

Ignoring Existing Customers

The method above will create new customers based on the email address, but it will also update customer information if it finds an email match.

If you don’t want the import to update any information on the customer if it finds an email match, then you can use the Target Restrictions tab and put the following:

2016-10-21-16-46-57

This will ensure that no customer information is updated when it finds an existing customer with the same email address.

But there is a trick to get this to work when you actually run the import scenario.

If you are doing a one-time import using the Import by Scenario (SM206036) screen, then you have to uncheck the Break on Incorrect Target checkbox on the Details tab. If you don’t do this, then the import will stop running after it encounters the first customer email address that already exists in Acumatica.

2016-10-21-16-55-26

If you are scheduling the import to run automatically in the Automation Schedules (SM205020) screen, then you need to do the same thing (uncheck the Break on Incorrect Target checkbox) on the Filter Values tab.

2016-10-21-16-57-22

Filed Under: Acumatica Learning Tagged With: Acumatica, Acumatica Blog, Acumatica Import Scenarios, Acumatica Learning, Acumatica Training, eCommerce, Import Scenarios, Importing Customers, Magento

By using this website, you agree to our Terms of Use (click here)
Building Generic Inquiries & Pivot Tables

Online Members

 No online members at the moment

Recent Blog Posts

  • EP 171: Automating Acumatica Sales Orders with Artificial Intelligence (Podcast) April 23, 2026
  • EP 170: Unboxing AI Assistant in Acumatica 2026 R1 (Podcast) April 19, 2026
  • EP 169: Laura Jaffe – Unlocking Acumatica Report Designer (Podcast) April 8, 2026
  • EP 168: Joe DiPaolo – Hosted Acumatica and Joe’s Jr. AI Developers (Podcast) March 31, 2026
  • EP 167: Nicole Ronchetti – A Claude Skill for Acumatica ERP (Podcast) March 27, 2026

Recent Forum Posts

  • cschwark

    Nested SubReport Issue

    I have a custom Shift Changeover Checklist report (AM64...

    By cschwark , 6 days ago

  • tmac

    RE: Can't export GI's to excel that contain the FATrans DAC after upgrade to 2025 R1 in less than 25 min

    I've had a similar issue with the out-of-the-box Fixed ...

    By tmac , 4 weeks ago

  • Ed Dolan

    RE: Limited or no support from Acumatica?

    @jjbotes Good thoughts. We'll endeavor to find a soluti...

    By Ed Dolan , 2 months ago

  • Johan Botes

    RE: Limited or no support from Acumatica?

    The question is "when" in the business process does the...

    By Johan Botes , 2 months ago

  • Ed Dolan

    RE: Limited or no support from Acumatica?

    @jjbotes Thank you for the feedback. I will discuss wit...

    By Ed Dolan , 2 months ago

  • Johan Botes

    RE: Limited or no support from Acumatica?

    Acumatica can have positive units in stock but a negati...

    By Johan Botes , 2 months ago

  • Ed Dolan

    RE: Limited or no support from Acumatica?

    @azeigler I am concerned as well about the lack of s...

    By Ed Dolan , 2 months ago

  • Johan Botes

    RE: Limited or no support from Acumatica?

    Hi Ed - the principle is embedded in standard functiona...

    By Johan Botes , 2 months ago

  • Ed Dolan

    RE: Limited or no support from Acumatica?

    Johan, Thanks for the rely and I hope you are well. ...

    By Ed Dolan , 2 months ago

Terms of Use & Disclaimers :: Privacy Policy

Copyright © · AUG Forums, LLC. All rights reserved. This website is not owned, affiliated with, or endorsed by Acumatica, Inc.