Migrate from OneSignal
Move push traffic from OneSignal to ComRaid.
Import a OneSignal Audience CSV into ComRaid via the Dashboard. Supports dashboard exports and API-style columns, including Contact and Endpoint Properties.
Dashboard CSV import
V1 migration uses a Dashboard CSV upload under Contacts → OneSignal Import. There is no CLI importer.
- Upload either a OneSignal dashboard Audience export or an API-style CSV (columns below).
- Dry run is the safe default: it returns a summary and row-level error report without writing data.
- Apply writes Contacts, Endpoints, Attributes, and push opt-outs. Re-runs overwrite Properties present on the row and stay idempotent by active push token (
(provider, provider_identifier)).
Export shapes
Both shapes use the same importer. Prefer the file OneSignal already gave you from Audience export; reshape only if you are building a minimal CSV by hand.
| Shape | Token | Platform | External user ID |
|---|---|---|---|
| Dashboard Audience | push_token | channel (e.g. Google Android) | external_id (alias external_user_id) |
| API-style | identifier / token / push_token | device_type (0=iOS, 1=Android) / platform | external_user_id (alias external_id) |
Android channel values such as Google Android (and FireOS-like) map to android Endpoints; Apple / iPhone / iPad map to ios. Email, SMS, and web push rows are skipped with a row error (unsupported_channel); sibling push rows still import.
Property mapping summary
First-class OneSignal columns become Contact or Endpoint Properties (not Attributes). Custom tags JSON becomes typed Contact Attributes. Unsubscribed rows create a push channel opt-out on the Contact.
| CSV column | ComRaid |
|---|---|
timezone_id | Contact timezone Property |
language_code | Contact language Property |
country | Contact country Property |
first_session | Contact + Endpoint first-seen Properties |
last_active | Contact last-active + Endpoint last-seen |
app_version | Endpoint first/current app version |
device | Endpoint model / OS / OS version (when parseable) |
sdk_version | Endpoint sdk_version |
sessions | Endpoint session_count |
tags (JSON object) | Contact Attributes |
subscribed No/false/0 or unsubscribed_at set | Contact push channel opt-out |
- Rows without an External user ID create anonymous Contacts (targetable by Endpoint id).
- iOS/APNs rows may set
apns_environment, or use the Dashboard default (sandbox / production). phone_numberandemailare ignored for write (V1 is push-only). Orphan OneSignal columns such asplayer_idare ignored and are not turned into Attributes.
API-style example
identifier,device_type,external_user_id,tags
ios-device-token,0,user_42,"{""plan"":""pro""}"
android-device-token,1,user_99,"{""plan"":""free""}"
anon-token,1,,After import
Imported Endpoints appear under Contacts / Endpoints and can be targeted in Message sends by external_user_id or Endpoint id (anonymous Contacts). See Contacts and segments and the Notifications guide.
Configure FCM and APNs credentials before sending to imported Endpoints — see Push providers. The import stores tokens; it does not verify them with the provider.