How to Migrate From Periskope to Tenashi
Periskope is genuinely good at what it was built for: managing high volumes of WhatsApp groups and multiple numbers in one structured workspace. If your ops team is running twenty groups at once and needs to keep them organised, labelled and searchable, Periskope delivers that well.
Teams move on when the missing pieces start to matter. There's no built-in sales pipeline, so the leads that come through those group conversations have to be tracked somewhere else. There's no native ticketing, so support issues that need SLA accountability fall out of the WhatsApp workspace entirely. And the catalog — sharing products directly in chat — isn't there.
If you've hit those limits and want to consolidate the full conversation-to-close journey in one tool, this is the migration path from Periskope to Tenashi.
Why Periskope users start looking elsewhere
Periskope's design focuses on group management and multi-number ops. That's a real and underserved need, and it's what the product does well. The gaps tend to surface when:
- You need deal tracking. A lead who replied in a group or DM needs to go somewhere — a stage, an owner, a close date. Periskope doesn't have this, so it goes to a spreadsheet.
- Support needs accountability. A customer complaint or post-sale issue needs a ticket with an SLA, not just a tagged message in a thread.
- You want products in the chat. Sharing product cards from a catalog while in a WhatsApp conversation isn't something Periskope does.
None of these gaps make Periskope bad — they're just outside its design intent. If your team has grown to where you need the full sales-and-support loop, that's when Tenashi makes sense.
What changes — and what doesn't
The migration from Periskope is simpler than most because Periskope already connects as a linked device, just like Tenashi does. Neither tool runs on the WhatsApp Business API. This means there's no API release step, no Meta Business Manager to navigate, and no waiting period.
| On Periskope | On Tenashi | |
|---|---|---|
| Connection method | Linked device (QR) | Linked device (QR) |
| Shared team inbox | Yes | Yes |
| WhatsApp group access | Yes | Yes |
| Built-in sales pipeline | No | Yes, with deal stages |
| Support tickets with SLA | Add-on only | Included |
| Product catalog | No | Yes |
The clean upgrade: you keep everything that works (shared inbox, groups, linked device) and add the pieces that were missing.
Step-by-step: migrating from Periskope to Tenashi
1. Export your contacts
In Periskope, export your contact list as a CSV. Note down any labels, tags or segments you've used to organise contacts — you'll recreate these as custom fields or tags in Tenashi. Chat history isn't exportable, so note any critical threads or conversation summaries.
2. Decide on your number
Because Periskope uses a linked device (not the API), the transition is simpler than for API-based tools. You just need to unlink your number from Periskope before linking it to Tenashi:
- Same number. Disconnect the existing device link in Periskope (Settings → Linked Devices or equivalent), then scan the QR code in Tenashi on the same phone. Brief window of disconnection during the switch.
- Second number. If you run multiple numbers, you can link one to Tenashi first, test it, and move the others one at a time.
3. Connect your number to Tenashi
Start your Tenashi trial and open the connect screen. Scan the QR code with the WhatsApp app on the phone holding your number — the same QR-link flow Periskope used. Your number is now live in Tenashi's shared inbox within a minute. Groups appear automatically.
4. Import contacts and rebuild your setup
Upload the CSV. Then build the structure Periskope didn't provide:
- Deal pipeline — create the stages that match your sales cycle.
- Custom CRM fields — source, industry, deal size, priority.
- Product catalog — add your products so agents can share cards in chat.
- Support ticket settings — SLA targets, categories, agent queues.
- Canned replies — quick responses for your most common messages.
- Automations — routing by keyword, auto-assign by group or contact tag.
5. Recreate group organisation
In Tenashi, WhatsApp groups appear in the inbox alongside DMs. Assign group conversations to specific agents or teams, add internal labels to organise by project or geography, and set up routing rules so new group messages land with the right person.
6. Bring your team in
Invite your agents and assign open conversations. Run through a test support ticket, add a test deal to the pipeline, and share a product card from the catalog in a test chat. Once you're confident the setup is solid, cancel Periskope.
Where Tenashi fits
Tenashi is built for teams that need WhatsApp as a complete sales and support workspace — not just a structured group manager. The shared inbox and group access that you already have in Periskope come along for the ride. What you gain:
- A sales pipeline so every lead has a stage, an owner and a next action.
- Support tickets with SLA so post-sale issues have accountability, not just a tag.
- A product catalog to share products in chat and link them to deals.
- One tool for the full journey — from first message in a group to closed deal or resolved ticket.
Pricing: Starter $18/mo, Growth $27/mo, Scale $56/mo, 3-day Growth trial, no card needed.
Start your free trial → · See every feature
FAQ
Do I need to release my number from an API when leaving Periskope?
No. Periskope connects as a linked device, not through the WhatsApp Business API, so there's no API deregistration required. You simply disconnect the link in Periskope and reconnect it in Tenashi by scanning a QR code.
Will my WhatsApp groups carry over?
Yes. Your WhatsApp groups belong to your number, not to Periskope or Tenashi. When you link your number to Tenashi, all the groups you're part of appear in the shared inbox automatically.
Does Tenashi handle multiple WhatsApp numbers?
Yes. You can link additional numbers to Tenashi so your team manages them all from the same workspace with shared assignment and internal notes.
What do I lose by leaving Periskope?
Periskope's depth in group organisation and multi-number operations at high volume is its core speciality. If managing dozens of groups with granular labelling and archiving across many simultaneous numbers is your primary need, Periskope is tuned for that. Tenashi's strength is a fuller sales-and-support lifecycle — pipeline, tickets, catalog — across a shared WhatsApp inbox that also handles groups.
Can Tenashi manage member lists in WhatsApp groups?
Yes. Because Tenashi links your real WhatsApp number, you can read, reply and manage members in your groups directly from the shared inbox.
Moving from Periskope to a full sales-and-support workspace? Start a free trial and link your number to Tenashi in the same QR-scan flow you already know — plus a pipeline, tickets and catalog that weren't there before.