Trust

Security

Last updated: October 16, 2026

SuiteMigration moves accounting data between systems you control. This page describes how we build and operate the Software to protect your data.

This page is provided for information. It describes how our systems are designed as of the date above, is not a warranty or a contractual commitment, and may change as our infrastructure and practices develop. Our binding commitments are in our Terms of Service, Data Processing Agreement, and Privacy Policy, which control in the event of any inconsistency with this page.

1. Our Approach

We use your data only to provide the Software. That includes running your migration or Migration Readiness Audit and providing related security and support. We do not mine, sell, rent, or license Customer Data. These are contractual commitments in Section 7.1 of our Terms of Service.

2. What We Process

Once you connect your source system, SuiteMigration retrieves the supported accounting records in read-only mode, including records you may choose not to migrate. The records available depend on your source system and connection permissions. They can include master data, transactions, employee records, tax rates and tax payments, cash expenses, reports such as the trial balance and profit and loss, and metadata such as terms, payment methods, departments, categories, and custom fields. The exclusions are described below.

The Migration Readiness Audit uses these records to count transactions and line items, identify undeposited payments, and find duplicates. We retain them for reconciliation and changes to your migration scope.

  • Employee records: employees referenced by transactions must exist in the destination system before those transactions can be recreated.
  • Reports: we use your source system’s trial balance, profit and loss, and similar reports to reconcile the migrated data.

Employee and vendor records can carry more than a name. Depending on your source system, an employee record may include a Social Security number, date of birth, home address, and payroll details, and a vendor record may include a tax identification number. Some source systems mask the most sensitive of these before sending them. QuickBooks Online, for example, masks employee Social Security numbers and vendor tax identification numbers, so we don’t receive the full number. We store whatever a source system sends. From Xero, we retrieve no employee or payroll records at all, because the access we request doesn’t include Xero’s payroll permissions.

The Software does not retrieve file attachments. Receipts, scanned bills, contracts, and other attached documents stay in your source system.

We also hold the mappings you define, the reconciliation output, the records written to your destination system (for example, NetSuite), and the account information of the users you authorize.

You control your source and destination systems and authorize their connections. Your agreements with those providers govern your use of them; they are not our sub-processors under our Data Processing Agreement.

3. Hosting and Infrastructure

By default, the Software runs on AWS in US East (Northern Virginia), where your data is stored. Enterprise customers may enquire about UK or EU data residency.

Our local, development, and production environments operate in separate AWS accounts, and Customer Data is stored only in the production account. The local account supports development on our own machines and holds only the secrets that work needs; it runs no application infrastructure or database. Human access to AWS is centrally managed through AWS IAM Identity Center using individual identities protected by multi-factor authentication. Permission assignments restrict personnel to the AWS accounts and roles required for their work.

The application runs on AWS Elastic Beanstalk across separate web and background-worker environments. Customer Data is held in a managed Aurora PostgreSQL database, with a managed Redis cache holding transient job state. Both sit in private subnets spanning two availability zones and are not reachable from the public internet: the database has no public endpoint, and network rules permit connections only from the application’s own compute — never from an IP address range. Only the load balancer is publicly exposed.

Requests to our API pass through AWS WAF before reaching the application. It blocks traffic originating from certain countries, filters requests from IP addresses on AWS’s managed reputation and DDoS lists, and rejects requests probing for common credential and configuration paths. WAF request logs are written with authorization headers, cookies, API keys, CSRF tokens, and query strings redacted, so credentials do not appear in them. Amazon GuardDuty provides continuous threat detection on the account holding Customer Data, and AWS Config continuously records the configuration of our AWS resources.

AWS is responsible for physical infrastructure security, including data-center controls, hardware and media disposal, host and hypervisor isolation between tenants, and the physical network. Its infrastructure certifications are listed in Section 14.

We are responsible for configuring AWS services, building the application, controlling access, and protecting Customer Data.

4. Tenant Separation

Your workspace is the boundary between your data and everyone else’s. Your projects, migrations, connections, and every record we pull from your accounting system belong to your workspace.

The Software determines your current workspace from your login. Changing a URL or an API call cannot grant access to another workspace. Switching workspaces requires an active membership, which we check when you switch.

When a request names a project, migration, or connection, the Software checks it against your workspace before returning anything, so a request can’t reach anything outside it.

5. Encryption

Connections to the Software use TLS 1.2 or higher. Older protocol versions are refused, and a request made over plain HTTP is redirected to HTTPS. Your session cookies are marked so that browsers send them only over encrypted connections. When the Software talks to the accounting systems you connect, it does so over HTTPS. Inside our environment, the cache that holds transient job state accepts only encrypted connections.

Every place we store Customer Data is encrypted at rest. That covers our database, its backups and snapshots, and the cache. The database is encrypted with keys held in AWS Key Management Service and managed by AWS.

6. Credentials for the Systems You Connect

To run a migration, the Software needs access to your source system and your NetSuite account.

We connect to QuickBooks Online and Xero over OAuth 2.0 using scoped, revocable tokens. For NetSuite, we use OAuth 2.0 for REST web services and token-based authentication for SOAP web services. Our Xero permissions allow read-only access to transactions, contacts, and settings. Conductor brokers QuickBooks Desktop and Enterprise connections, so we do not hold your accounting credentials for those systems. Conductor is listed on our Sub-processors page. We also hold refresh tokens to keep OAuth connections active during migrations.

The application encrypts connection credentials, including refresh tokens, using authenticated encryption before storing them in the database. Key material is held in AWS Secrets Manager. This encryption is independent of the database’s storage encryption, so backups and snapshots contain only ciphertext for these fields. Multi-factor authentication secrets receive the same protection.

Connection credentials are hidden from our staff administrative interface. Staff can see the connected system and company, but cannot view credentials through that interface.

You can delete a Connection at any time. This immediately disables its use, and its stored credentials are then deleted from our database. Encrypted copies may remain in backups until those backups expire. To revoke access at the provider, disconnect SuiteMigration within your source system or NetSuite.

7. Application Access and Authentication

Access to SuiteMigration starts with an invitation from a workspace admin. The invitation belongs to the email address it was sent to; you use that address and a password to sign in.

You can add multi-factor authentication to your account. When you set it up with an authenticator app, you receive backup codes for signing in if you lose the app. Admins can see who has enabled MFA.

Every workspace member can create projects, connect systems, and run or delete migrations. Only admins can invite people, change another member’s admin status, deactivate members, rename the workspace, and view its activity log.

We manage your session with secure cookies accessible to SuiteMigration only. Your session remains active while you use SuiteMigration and eventually expires if left unused. Signing out removes the cookies from your browser.

We store passwords as salted hashes, never in readable form. Passwords must meet a minimum length, and repeated failed sign-in attempts temporarily block further attempts on the account.

Workspace admins can review an activity log of recorded changes to members, invitations, projects, connections, data pulls and pushes, and field mappings. It also records password resets by members.

8. Secure Development

Changes to the Software reach production through a pull request, and a pull request into production needs a reviewer’s approval before it can be merged. Direct pushes and history rewrites are blocked on the branches that deploy to our development and production environments, and getting into our code repository takes multi-factor authentication.

A change goes through our development environment before it reaches production. Lint checks and automated tests run on pull requests, and production releases are deployed by an automated pipeline.

If a third-party library we depend on is hit by a publicly known vulnerability, we get an automated alert.

9. Logging and Monitoring

We use application logs and error and performance monitoring to detect faults, support production operations, and investigate security events. We do not maintain a record-level log of Customer Data viewed through Django Admin.

10. Internal Access to Customer Data

Access to production systems and Customer Data is limited to personnel with a business need, and is removed when someone’s role changes or they leave.

Most of our developers can access Customer Data through the Software’s production administrative interface for maintenance, support, and troubleshooting.

Changes made through the administrative interface are subject to the Software’s validation and controls.

Access to the administrative interface is controlled within the Software, separately from AWS infrastructure access.

11. Staff Authentication

Our internal systems run on Google Workspace, configured so that multi-factor authentication is required on all staff accounts.

12. Sub-processors and Vendors

Our Sub-processors page lists every third party that processes Customer Data, its role, and the data it receives. Our Data Processing Agreement references this list.

Our sub-processors are engaged under written terms requiring data-protection obligations materially consistent with our DPA.

13. AI and Your Data

We do not use your data to train AI models, and we do not let anyone else use it for that either. This is a contractual commitment in Section 7.3 of our Terms of Service.

The Software includes an optional AI feature that suggests field mappings. It runs only when you choose to use it for a specific mapping task. Requests are processed through Amazon Bedrock in our AWS environment. AWS states that Bedrock does not store inputs or outputs, share them with model providers, or use them for training.

14. Compliance and Certifications

AWS maintains SOC 1, SOC 2, ISO 27001, and PCI DSS attestations covering its infrastructure and publishes them through AWS Artifact.

We do not currently hold a SOC 2 or ISO 27001 certification of our own.

We are working toward SOC 2 Type II. We use a compliance-automation platform to document our policies and monitor our controls.

15. Data Retention and Deletion

We keep your data after go-live so you can reference it, compare against it, or run a further migration from it.

You can delete a Migration through the Software whenever you want. We may also discontinue access to a Migration that is subject to Fees, as permitted by Section 2.6 of our Terms of Service and on the notice required there. When a Migration is deleted, or when its access is discontinued, we delete the Customer Data associated with it, as described in Section 7.6.

For a Migration that has not become subject to Fees and has no signed Order Form, we may delete its Customer Data at any time after 12 months from its Migration Start Date, also under Section 7.6.

Separately, on termination or expiration of the Agreement or any applicable Order Form, we delete or return Personal Data under Section 11 of our Data Processing Agreement.

In each case, deleted data may remain in backups, logs, or similar records for a limited period before it is fully purged, and longer where applicable law requires us to keep it.

16. Incident Response

If we confirm a security incident affecting your data, we will notify you without undue delay and take reasonable steps to mitigate it. Our specific obligations are set out in Section 7.2 of our Terms of Service and Section 10 of our Data Processing Agreement.

17. Availability and Continuity

Our application infrastructure is configured across multiple Availability Zones, allowing application instances to run in separate data centers within the same region.

We back up your data. Our database uses automated, encrypted backups. Point-in-Time Recovery (PITR) allows us to restore the database to an earlier point if data is lost or accidentally changed.

18. Reporting a Vulnerability

If you believe you have found a security vulnerability in the Software, please tell us at security@suitemigration.com. We will acknowledge your report and work to understand and address the issue, and we will not pursue action against researchers who report in good faith, avoid privacy violations and service degradation, and give us reasonable time to respond before disclosing publicly.


Questions: support@suitemigration.com. Related: Terms of Service · Data Processing Agreement · Privacy Policy · Sub-processors.