paasaplatformtransfer

How to Transfer RSUs from Paasa to Rovia

Paasa is one of the newer entrants in the India-side US equity space. The migration template to Rovia — data export, partner-broker exit, lot reconstruction — is the same shape; the platform-specific details are worth verifying.

Rovia Editorial·5 June 2026·7 min read

The Paasa context

Paasa is one of the more recent additions to the Indian-resident-facing US equity space. Like several others in the category, it operates on a partner-broker model — UI, INR onboarding, India-side compliance helpers wrapped around an underlying US custodian.

For self-directed US equity buying, that's reasonable. For users whose primary US equity inflow is employer RSUs from Schwab / Morgan Stanley / Fidelity / E*TRADE — with the associated need for vest-day INR cost basis, ESPP tracking, per-lot 24-month LTCG countdowns, and calendar-year Schedule FA in ITR-2 format — a dedicated RSU platform usually fits the workflow better. This guide is for that switching cohort.

Because the Indian fintech space evolves quickly, do not take any specific Paasa fee, FX rate, or feature claim in this guide as authoritative — always verify in your live account or with Paasa support. The mechanics below are the general pattern that applies to most Indian-platform-to-Rovia migrations; platform-specific specifics belong on the platform's own pages.

1. The migration paths

Path	How it works	Trade-off
In-kind transfer	If Paasa's partner broker supports external ACATS, positions transfer with cost basis preserved	Preserves 24-month LTCG clock; depends on partner-broker policy
Sell + remit + rebuy	Liquidate at Paasa, withdraw INR to Indian bank, rebuy through Rovia's linked US custodian	Always available; resets cost basis and 24-month clock
Dual-run during transition	Keep Paasa positions in place, route future RSU vests through Rovia from grant day	No immediate tax event; two platforms to reconcile during overlap

The decision logic is covered in depth in the Broker Transfer pillar. The short version: if positions are appreciated and LTCG-eligible, in-kind or dual-run is materially better than sell-rebuy. If positions are small or below cost, sell-rebuy is operationally simpler with minimal tax impact.

2. The data extraction step

Regardless of path, the same four exports from Paasa before initiating:

Full transaction history — every buy, sell, dividend, fee. Date and price per row.
Per-lot cost basis report — acquisition date and USD price for each lot still held.
Year-end tax statements — both US-format (1099-equivalent if produced) and India-format summaries.
Any Schedule FA exports the platform has generated for past ITRs.

Keep these locally. They are the audit trail for any future ITR queries and the basis for reconciling your post-migration inventory.

3. The Rovia-side setup

Open the Rovia account: rovia.one → KYC and W-8BEN.
Upload the Paasa transaction history. Rovia reconstructs per-lot INR cost basis at the actual RBI TT reference rate on each original transaction date.
If Path 1 (in-kind): coordinate the ACATS with both platforms; settles in 5–7 business days at the US-custodian level. If Path 2 (sell-rebuy): execute the Rovia-side rebuy. If Path 3 (dual-run): no immediate action — future RSU vests flow into Rovia from your employer broker.
Reconcile final inventory: Rovia-imported lots vs Paasa-side positions before closing or reducing the Paasa account.

For users who came to Paasa from an employer-broker plan with existing RSUs already moved over, the original vest dates are the meaningful anchor — not the Paasa-onboarding date. Rovia's lot importer preserves the original vest date for capital-gains purposes, so the 24-month LTCG clock continues from the original grant's vest day, not from a later platform-change date.

4. After migration — what becomes easier

Per-lot INR cost basis at the actual RBI TT rate on each original transaction date — not platform-internal rates.
Multi-employer-broker support — direct ingestion from Schwab Equity Awards, Morgan Stanley StockPlan, E*TRADE Stock Plans, Fidelity Stock Plan Services.
Schedule FA in ITR-2 calendar-year format with peak-value computed per lot — covered in Schedule FA pillar.
24-month LTCG clock per lot with month-23 alerts and the post-Finance-Act-2024 rate engine — see Vest-Cycle Strategy.
Form 67 automation for dividend-receiving employees — see Form 67 pillar.
0-markup FX channel on repatriations — see FX & Repatriation pillar.

Frequently asked questions

Why move from Paasa to Rovia?

Indian US-equity platforms vary in how deeply they support RSU-specific workflows — multi-broker statement ingestion (Schwab / Morgan Stanley / Fidelity / E*TRADE), per-lot INR cost basis at original vest-day RBI TT rates, ESPP discount handling, calendar-year Schedule FA with peak-value per lot, automatic Form 67. If your usage is RSU-heavy, a dedicated RSU platform tends to fit better. Self-directed users often have less reason to switch.

Can I transfer positions in-kind from Paasa?

Depends on Paasa's current partner-broker arrangement and external-transfer policy. Always verify in your live account; capabilities in the Indian fintech space evolve.

Will my Paasa transaction history transfer?

Export Paasa's transaction CSV before initiating closure. Rovia ingests the CSV and reconstructs lot-level INR cost basis using the original transaction dates and RBI TT rates. The original dates and prices are facts, preserved; the INR basis is reconstructed.

What about my Schedule FA filings from past years?

Past filings are between you and the IT Department, not platform-specific. Future filings continue from Rovia's reconstructed lot inventory. Reconcile your final Paasa position list against your Rovia-imported list before closing.

How long does the full migration take?

Most Indian-platform migrations complete in 2–4 weeks: 1–2 weeks for data export and Rovia-side onboarding (KYC, W-8BEN), 1–2 weeks for Paasa-side liquidation or transfer settlement.

Do I have to close my Paasa account?

Not necessarily. You can stop using the US equity module while keeping the account open if Paasa offers other features you use. Migration and account closure are separate decisions.

Last reviewed June 5, 2026. Paasa's features, fees, and partner-broker arrangements change frequently — verify in your current account before initiating a migration. Informational only, not personalised tax or financial advice. Paasa is a registered trademark of its respective owner.

← All posts