For AI agents: the complete documentation index is available at https://docs.clickmax.io/en/llms.txt, the full documentation bundle is available at https://docs.clickmax.io/en/llms-full.txt, and this page is available as Markdown at https://docs.clickmax.io/en/guides/migrate-your-contact-base.md.
  • English

      • How do I bring my contact base over from another platform?

      Importing contacts is the first thing almost everyone does when migrating — and the step where most data gets ruined. An hour spent preparing the file saves weeks of a dirty base.

      Before you start

      • Role: Owner, Admin or Editor.
      • Check how many contacts your plan allows before importing — see the contact limit (Portuguese).
      • You need a lawful basis to process these contacts. The import asks you to confirm that the contacts were obtained in line with data protection rules — see data protection in practice.

      1. Export from the old platform

      Export as CSV, with as many fields as you can. It is far easier to drop a column later than to go back and export again.

      2. Prepare the file

      Before uploading:

      • Every column needs a header — that is what the mapping works from.
      • Use one consistent date format. The import screen states the expected format for date fields is YYYY/MM/DD.
      • Phone numbers in a consistent pattern, including the country code.
      • Remove rows with no email and no phone: a contact with no way to contact them is worth nothing.
      • Resolve duplicates here, in the spreadsheet. It is far easier now than later.

      3. Decide the tagging before you import

      Apply a tag identifying the source and the batch — the old platform and the date, for example. Without it, three months from now you will not know who came from the migration and who arrived afterwards.

      If your base has distinct groups, import them as separate batches with different tags rather than all in one go.

      4. Import and map

      Follow import your first contacts. On the Map fields step, check column by column — automatic mapping gets the obvious ones right and the rest wrong. Fields that do not exist yet can be created with Add custom attribute, or set up beforehand as custom fields (Portuguese).

      5. Check the result

      Once the import finishes, open a handful of contacts and confirm the values landed in the right fields. If something went wrong, it is much better to find out with 20 contacts checked than with 20,000 imported.

      6. Clean up what's left

      Duplicates and invalid records that slipped through: see clean up your database.

      If it didn't work

      • Columns came in empty: the header does not match — review the mapping and reimport the batch.
      • Dates rejected: use the format stated on the import screen.
      • You hit your plan limit part-way through the import: see the limits and quotas reference (Portuguese).