What moves, and in what order
Most moves follow the same order: verify your sending domain, bring your contacts and their consent, keep your tracking flowing, then rebuild templates and journeys. Keep your current tool running while you test Kirora, then plan a controlled handover for each campaign and journey.
1. Verify your sending domain
Add Kirora’s SPF and DKIM records to your domain so email comes from you. New workspaces start with a modest daily sending limit that grows as your list proves clean, so start early and send to your most engaged people first.
The deliverability guide explains why.
2. Bring your contacts and consent
- From a spreadsheet: export from your current tool and import the CSV, mapping each column to a contact field, attribute or date.
- From your systems: send contacts in batches over the API, using your own IDs so nothing is duplicated.
- Consent comes with them: import who agreed to email and push, and where that agreement came from. Kirora never assumes consent.
- Groups: recreate your lists as groups, then build segments for anything rule-based.
3. Keep your tracking flowing
If another engagement platform already receives your people and events, Kirora accepts the same tracking calls in the most widely used formats. Point them at Kirora and send to both tools while you move. Opt-outs carry over; opt-ins never do.
Otherwise, call identify and track from your backend. Keep your event names: journeys can trigger on whatever you already send. See identify and track.
4. Rebuild your emails
Set your brand colours and fonts once in the email designer’s theme, then rebuild your key emails from blocks. Shared blocks keep your header and footer consistent, and Kiro AI can draft a first version for you to edit.
5. Recreate your automations
Each automation becomes a journey: the same trigger event or date, then waits, branches and sends. Turn on each journey in Kirora as you switch the old one off, and check entry rules and existing enrolments to reduce duplicate messages during the handover.
6. Connect payments
Connect your payment provider and successful payments arrive as “Order Completed” events, ready for the conversion goals and revenue reports you configure. See integrations.
Need a hand?
Tell us what you’re moving from and roughly how big your list is, and we’ll help you plan it: hello@kirora.io.