CRM settings & data import
Timezone and business details, and moving your fields, tags, lists, templates and contacts across from another email tool.
Settings has three tabs: General, Email sending, and Import.
General
Regional settings
Your timezone. It's used for scheduled broadcasts and for reporting dates — so a broadcast scheduled for 9am goes out at 9am your time, not the server's or the reader's. Set it before you schedule anything.
The Time format next to it — 24-hour · 16:00 or 12-hour · 4:00 PM — is how times appear on booking pages, in booking emails and across the CRM. One Save keeps both.
Business details
| Field | |
|---|---|
| Business name * | The legal or trading name |
| Logo * | Your mark |
| Address, Country, City, State / province, ZIP * | A real postal address |
| Support email / phone | How customers reach you |
Fields marked * are required.
Caution
Email won't work without these. You can't create messages, broadcasts or automations until the required business details are saved — you'll be sent here with a warning and returned to where you were afterwards.
That's not an arbitrary gate: anti-spam law in most countries requires a real postal address in commercial email, and these details are what fills the footer. They also appear on customer receipts.
Import from an autoresponder
The Import tab moves your data out of another email tool and into the CRM. It's the migration path — the counterpart to connecting an autoresponder, which leaves your list where it is.
Running an import
- Pick a source. Each one is badged Connected, Keys needed, or Connect via OAuth.
- Provide credentials if it needs them. You can save them as the project's connection so you don't re-enter them next time.
- Choose what to import. They're processed in a fixed order — custom fields → tags → lists → email templates → contacts — so that by the time contacts arrive, everything they refer to already exists.
- Add new contacts to lists and tags, optionally. This applies only to contacts that aren't already in the project — your existing base isn't re-tagged or moved.
- Start the import. It runs in the background: Queued → Running → Completed (or Failed), with live progress and, at the end, a per-entity summary and any errors.
Past runs stay in the history below, so you can see what was brought across and when.
Caution
Importing contacts fires your active automations — anything triggered by contact created or list subscribed. Pause those before a large import.
What to expect from each source
Every tool models things slightly differently, so some data can't come across cleanly. These are known and expected, not faults:
| Source | What to know |
|---|---|
| Mailchimp | Lists map to audiences. Templates come from campaigns and saved templates; campaigns with the same name are de-duplicated |
| ActiveCampaign | Suppression there is per-list — a contact stays sendable while active on any list, so review your suppressions after importing |
| ConvertKit (Kit) | No lists — forms import as lists, but the contact↔form links don't carry over. Segmentation lives on tags. No last name or phone |
| GetResponse | Unsubscribed contacts aren't exposed, so everything imports as active — check before your first send. Tags and fields are fetched per contact, so large imports run slowly |
| AWeber | Custom fields have no types there, so they all arrive as text. Templates come from broadcasts |
| Ontraport | Lists map to Groups; templates map to messages of type Template |
Caution
The GetResponse and ActiveCampaign notes matter most. In both cases people who opted out can arrive looking sendable — and emailing them produces exactly the spam complaints that damage your sending reputation. After importing from either, check Suppressions and add anyone you know has unsubscribed.
After an import
- Check Suppressions — see above.
- Look at Contacts and confirm the custom fields landed where you expect.
- Check your Lists — names carry across, membership sometimes doesn't, in the cases noted above.
- Open an imported message before sending it. Templates survive the trip structurally, but not always beautifully.