---
title: Import customers into Tapmy
description: "How to import customers into Tapmy: clean your list, respect consent, test with a small sample, check the results and fix rejected rows."
lead:
  - Import customers into Tapmy only through the supported import flow, with a cleaned file and a legal reason to move the data. Test a small sample first, then check the results before importing the rest.
tags:
  - customers
  - digital-products
source: docs/tapmy-wiki/pages/import-customers-into-tapmy--0f172864.md
---

## Can I import, and what data is safe? {#before-you-start}

Check that import is offered on your plan and setup, and look at the live template for the format. This page does not define either.

Be sure you have a lawful source for the customer data and a reason to move it. Cut every column you do not need. Never import passwords, tokens, full payment data, ID documents, private messages, health information or internal risk notes. Keep a secure backup of the source file and limit who can open it.

## How do I prepare the file? {#prepare-the-data}

1. Clean up emails and trim stray spaces.
2. Split first and last names only if the template asks for it.
3. Use one row per person unless Tapmy says otherwise.
4. Remove duplicate emails and review shared or alias addresses by hand.
5. Put dates in the format the current template requires.
6. Keep marketing consent separate from customer status. Record the source and time only when you have real evidence.
7. Decide whether product access moves in the same flow or separately.
8. Delete empty, outdated or unsupported columns.

Buying on another platform does not prove someone agreed to your marketing now. And importing a customer is not a Tapmy order, so it should never create made-up revenue.

## How do I run a test import? {#run-a-controlled-import}

Pick a small sample that includes normal rows and known awkward ones. Use the current import flow and map only the fields you understand. Read any preview, validation, duplicate or error report before you confirm.

When the sample finishes, search for each test record. Check names, emails, consent, source and access. Make sure no existing Tapmy record was overwritten by surprise. Then import the next batch.

Keep a simple migration log: source system, export time, file version, row count, sample results, rejected rows, who did it and when it finished. Leave out customer data you do not need.

## What good looks like {#what-success-looks-like}

- The imported count matches accepted, rejected and skipped rows.
- No duplicate or unrelated records were overwritten.
- Consent rests on evidence, not on a past purchase.
- Access matches your migration plan.
- The source file and temporary copies follow your retention policy.

## When rows fail {#troubleshooting-and-limits}

Use the live error report and fix one cause at a time: invalid email, unsupported field, duplicate, bad date, encoding or file size. Do not re-import the full file again and again without checking whether partial records were created.

If there is no safe import path, do not fake orders or send the file to a service you have not vetted. Manual audience add is confirmed only on Max, which does not mean bulk import exists.

## Next steps {#next-steps}

Use **Search and filter customers** to check the cohort, **Grant or remove product access** for approved access fixes, and **Collect and manage marketing consent** for compliance. Contact [Tapmy Support](/help/tapmy-support) with a redacted sample and the exact error. Do not send the full customer file unless an approved secure process asks for it.