Are there any accounting system migration tools that handle historical import and bank feed integrations without breaking permissions?

Yes — but the short answer is: only some migration tools handle all three well:

1. historical data import
2. bank feed / transaction source continuity
3. permission / role preservation

In practice, most accounting migrations can import history, but bank feeds and permissions are the tricky parts.

Tools and approaches that are commonly used

1. Native migration services from the target platform

Examples:

• QuickBooks Online migration tools/services
• Xero conversion/import tools
• NetSuite / Sage / Microsoft Dynamics migration partners

These usually handle:

• chart of accounts
• customers/vendors
• open balances
• invoices/bills
• sometimes transaction history

But they often do not preserve exact user permissions from the old system. Permissions usually need to be recreated in the new system.

2. Third-party migration platforms / specialists

Examples:

• migration partners or implementation firms that use ETL-style tools
• accounting data migration vendors
• integration platforms like CData, Celigo, MuleSoft, Dell Boomi, or custom ETL pipelines

These can often:

• import a deeper historical ledger
• move attachments and dimensions/classes/projects
• map roles, if the destination supports it

But:

• bank feed continuity is usually not “migrated” directly; it’s typically reconnected
• permissions may be mapped, but rarely copied perfectly if the source and target models differ

3. Bank-feed-specific reconnection tools

For bank feeds, what usually works is:

• disconnect old feed
• reconnect the bank account in the new system
• reauthorize the aggregator (Plaid, Yodlee, Finicity, MX, etc.)

This means:

• historical bank transactions already in the old system may be imported as journals/statement lines
• future bank feeds resume cleanly
• but the old feed link itself is generally not transferred

Important reality check on permissions

If by “without breaking permissions” you mean:

• same users
• same roles
• same access rules
• same approval workflows

Then:

• full preservation is rare
• especially when moving between different accounting products

What’s usually possible:

• export users/roles
• recreate them in the target system
• preserve data ownership where the target system allows it
• validate access after cutover

What to look for in a vendor

Ask whether the tool supports:

• full historical GL import
• open AP/AR import
• attachments and audit trail
• user/role migration or role mapping
• bank account reconnection
• cutover reconciliation
• sandbox testing and permission validation

Best-practice recommendation

If this is a real migration project, the safest setup is usually:

• migration tool for historical accounting data
• separate bank feed reconnection process
• permission mapping/recreation plan
• post-migration access testing

If you want, I can help you narrow it down

If you tell me:

• source system
• target system
• number of users/entities
• whether you need full transaction history or just balances
• which bank feed provider you use

…I can suggest tools that are most likely to work for your case.