SetNow

Exporting clients from DIKIDI

Updated October 16, 2026 · 3 min read

DIKIDI exports the client base as an Excel or CSV file, and SetNow accepts it as is: export the base on a computer and upload the file — SetNow finds the columns it needs itself.

Export the base from DIKIDI

  1. Open DIKIDI Business in a browser on a computer and sign in to your project.
  2. In the left menu, choose Clients → Client list (in the Russian interface — «Клиенты → Список клиентов»).
  3. Click the three-dot button in the top right and choose a format — Excel or CSV. The file includes every client in the base.

In DIKIDI, only a user with Creator access («Создатель») can export the client base. If there's no export button, ask the project's creator to export the file or to pass this access to you.

The steps follow DIKIDI's help center as of October 2026; menu names may differ depending on the interface language. If the interface has changed, look for the export in the same Clients section.

Upload the file to SetNow

Open Clients → Client base, click Import and choose the file — see the step-by-step guide in Moving your client base. There's no need to re-save the file or delete columns, and the old .xls format works too.

From a DIKIDI export, SetNow takes the phone number, the first and last name and the comment. DIKIDI keeps the first and last name in one column — “Anna Miller” — and SetNow splits them itself. Totals, visit counts, discounts and other statistics aren't imported: SetNow builds them up again from new bookings.

Clients from the file are marked Visited before: this is your regular base, and the first-visit price isn't meant for them.

After the upload

  • Add upcoming bookings in the calendar and remaining memberships manually: the file carries contacts only.
  • Replace the booking link on Instagram, Telegram and your website with your SetNow link.
  • While you're moving, keep DIKIDI open to cross-check, and take new bookings in SetNow only.

How SetNow differs from DIKIDI in features and pricing — in the blog post Replacing DIKIDI.