What gets imported from v1
Campaigns, websites, presaves, fans, and related history import into SymphonyOS. Learn what may be partial and when to reconnect platforms.
The import wizard copies your Symphony v1 marketing footprint into SymphonyOS where supported. Expect campaigns, websites, presaves, fans, and related history to come across. Exact coverage depends on how your v1 account was set up.
Deliverables
- Ad campaigns and related metadata (Meta/TikTok connection presence may show in preview)
- Websites, mapped to sym.fm where applicable
- Presaves and release pages (legacy symphony.to URLs stay for existing releases)
- Fans and CRM history where the v1 data model supports it
Partial imports and re-sync
Some records may import partially if v1 data is incomplete or a platform changed since you last synced. Running import again tops up missing items rather than duplicating everything. If your team already uses v2, attach or resync flows can pull remaining brands or fresh activity from v1.
Connections after import
OAuth tokens do not always survive migration. Plan to reconnect Meta, TikTok, Spotify, and other platforms under Integrations in SymphonyOS before launching new campaigns or presaves. Preview screens may show whether v1 had a connection even if you must re-authorize in v2.
Import moves data into v2. It does not move v2 campaigns back to v1 or delete either side. Work you create in SymphonyOS stays in SymphonyOS.
What import does not promise
- Legacy v1 subscription pricing or discounts on SymphonyOS plans
- Automatic republication of every draft without review
- New sym.fm URLs for v1-only legacy fan pages that should stay on symphony.to