Travel Management Software Integrations: Accounting, HRIS, SSO and Expense Tools

Choosing travel management software means evaluating more than booking options and negotiated rates. Finance leaders need dependable billing data, travel managers need policy controls, and IT teams need an orderly way to manage employee access. Integrations determine how those responsibilities connect to the accounting, human resources, identity, and expense systems a business already uses.

The most useful comparison is not a count of integrations. It is whether each connection exchanges the right records, preserves the fields needed for reporting, and fits the company's approval and reconciliation processes. A booking confirmation, hotel folio, consolidated bill, card charge, and reimbursement are different financial records, even when they relate to the same trip.

Engine, a modern travel management platform, combines hotel, flight, and rental car booking with policy controls, centralized billing, reporting, and supported accounting integrations. Its HRIS, ERP, and SSO overview explains how additional connections fit into a company's technology environment. This guide covers the integration requirements that matter most, the relevant Engine capabilities, and a practical implementation sequence.

Key Takeaways

• Prioritize workflow coverage over connector counts. Establish which booking, billing, employee, card, and expense records move between systems, along with their destinations and posting rules.
• Treat accounting sync as a financial process. GL accounts, valid dimension values, statement timing, test bills, and exception handling determine how useful the integration is during reconciliation.
• Separate employee synchronization from travel policy administration. HRIS connections can maintain traveler profiles, while policy assignments and approvals remain deliberate administrative controls.
• Distinguish SSO from provisioning. Corporate sign-in, account creation, account archiving, and existing-session management are related but separate parts of the access lifecycle.
• Keep financial record types distinct. Itinerary information can support an expense workflow, but receipts, reimbursements, card transactions, and posted bills have separate purposes.
• Evaluate total operating effort. Setup, data mapping, testing, user training, monitoring, and ongoing maintenance affect the value of an integration alongside platform and optional product costs.

What Corporate Travel Management Software Integrations Do

Travel management software brings business trips into a governed booking environment. For conferences, sales visits, company offsites, and recurring employee travel, a platform can combine reservations with approval processes, reporting dimensions, and company payment arrangements. Integrations extend those workflows to the systems responsible for people, permissions, and financial records.

The Core Integration Challenge

Consider a sales employee booking a hotel for a conference. The booking creates a reservation and an expected cost. The completed stay can generate a hotel folio. Depending on the payment method, finance may also receive a company card charge or an itemized consolidated invoice. Accounting then applies the relevant general ledger account, department, and project information. An employee-paid expense may follow a separate reimbursement workflow.

These records arise at different times and serve different purposes. An itinerary import can populate trip details without creating a final accounting expense. A consolidated bill can carry approved cost information without serving as the employee's reimbursement claim. A reliable integration strategy identifies which system owns each record and how the records are connected for audit and reconciliation.

Engine supports this separation through documented billing-to-accounting connections and employee account synchronization. Its accounting setup maps selected billing fields into financial systems, while its HRIS integration updates traveler account information from the connected employee system.

Understanding Integration Depth

Four characteristics determine how a connection operates:

• Sync direction: A one-way connection moves selected information from one source to a destination. A two-way connection exchanges particular objects or reference fields in both directions. The description should identify the actual objects and operations, not rely on a broad label.
• Sync trigger: Event-driven transfers and scheduled jobs have different timing. Billing statements, employee roster updates, and individual booking events may each have distinct triggers.
• Field mapping: Department, class, project, cost center, vendor, currency, and other values must correspond to valid fields in the receiving system. Free-text fields and controlled accounting dimensions behave differently.
• Operational controls: Authentication permissions, duplicate handling, error visibility, retries, and record ownership support a controlled process after the connection is established.

For example, Engine's QuickBooks Online setup and NetSuite setup both import financial reference data for mapping and synchronize configured bills when billing statements are issued. This is more informative than describing the connections simply as two-way integrations.

Streamlining Financial Operations with Accounting Software Integration

Accounting connections help finance teams move eligible business travel billing data into the ledger process. Their primary value comes from consistent account coding, fewer repeated entries, and clearer tracing between statements and financial records.

How Accounting Integrations Support Travel Expenses

The benefits depend on the mappings and records selected for the business:

• GL categorization: Engine's QuickBooks invoice mappings distinguish transaction types such as lodging, incidentals, flights, rental cars, car insurance, Engine X, subscriptions, and adjustments. Finance can associate relevant types with the appropriate accounts.
• Department and project context: Compatible Engine custom fields can populate supported QuickBooks dimensions or NetSuite dimensions. This helps keep business context attached to a bill as it moves downstream.
• Supporting documentation: The QuickBooks Online setup offers an option to attach the Engine PDF invoice to the synchronized bill. Hotel folios and other supporting receipts remain identifiable financial documents within the wider accounting process.
• Sync visibility: Engine provides billing views for reviewing completed transfers and resolving mapping exceptions. Finance teams can connect their reconciliation work to recorded bill synchronization results.

These functions support more systematic month-end processing. Close-cycle improvement should be measured against a company's own transaction volume, exception rate, and reconciliation workload rather than assumed from the presence of an integration.

How Engine Connects to QuickBooks Online and NetSuite

Engine's published accounting directory includes QuickBooks Online, NetSuite, and Sage Intacct. The detailed QuickBooks Online and NetSuite setup guides document separate authentication methods and mapping workflows.

For QuickBooks Online, an Engine administrator starts the integration from Settings and authorizes a QuickBooks connection through Merge. Engine imports reference data such as vendors, the chart of accounts, and valid mapping values. The administrator selects applicable invoice types and uses simple or custom mapping. Simple mapping sends a bill total to a selected account, while custom mapping can assign individual line items to different accounts. The documented connection test uses a $0 invoice. See the QuickBooks Online guide.

For NetSuite, the setup uses SuiteCloud web services, a dedicated integration role, and token-based authentication. The guide recommends enabling token-based authentication and leaving OAuth 2.0 unchecked on the NetSuite integration record. Engine imports vendors, accounts, custom fields, and segments for its billing mappings. The configuration includes selection of one NetSuite entity for billing and a $0.01 test invoice. See the NetSuite setup guide.

Both documented setups are available to eligible accounts with DirectBill or Engine X enabled. After configuration, eligible bills synchronize when the next billing statement is issued. Engine's billing sync views provide status information and error-resolution workflows. Actual booking transactions can then be used to assess the configured custom-field values in normal financial processing.

Accounting Mapping Decisions That Matter

Before activating a financial connection, the finance owner should establish a documented mapping design covering:

• Invoice types and associated GL accounts.
• Vendor and chart-of-accounts reference values.
• Department, class, project, job code, and other required dimensions.
• Tax, currency, entity, and reporting requirements relevant to the organization.
• Treatment of credits, adjustments, corrections, and duplicate records.
• Ownership of errors, mappings, approval rules, and month-end reconciliation.

The important distinction is between recording a business travel transaction and applying the accounting treatment the business requires. Mapping rules make that treatment repeatable.

Enhancing HR Processes with HRIS Software Integration

HRIS integration connects personnel information with the traveler accounts used in a business travel program. It is especially useful when employees regularly join, transfer departments, change profile details, or leave the organization.

Synchronizing Employee Accounts and Profile Data

Engine's HRIS integration guide, updated in October 2026, documents connections through Merge to supported HRIS platforms, including Workday, BambooHR, and ADP. The integration provides a one-way flow from the HRIS into Engine and supports four employee lifecycle actions:

• Account creation: Eligible new employees receive traveler accounts using required fields such as first name, last name, email address, and employment status.
• Profile updates: Supported employee attributes, including selected department and contact information, can be refreshed from HRIS data.
• Account archiving: Employees marked as terminated are archived during the subsequent synchronization.
• Account restoration: Engine can restore a rehired employee's archived account when the email address matches exactly and the other identifying fields used for matching, including first name, last name, and employee ID, match the archived record. The HRIS integrations FAQ documents these criteria.

The initial synchronization starts after setup, and subsequent updates are scheduled approximately every 24 hours. Engine also offers selective synchronization using supported employee groups, such as department, division, or cost center. The available selection criteria depend on the connected HRIS and configuration.

Engine's standard mapping covers required identity fields and documented optional fields, including employee ID, phone number, and department or team. A cost center can serve as an employee group selection criterion where supported, which is different from automatically writing it into every traveler profile.

Connecting HR Data to Travel Policy Administration

Employee records help travel administrators maintain a consistent roster. Travel eligibility and booking permissions, however, also depend on employer-defined travel policies and roles.

Engine's HRIS integration guide explains that newly created members receive the default Traveler role and travel policy. The HRIS integration FAQ further clarifies that administrators manage Engine travel policy assignments directly, providing explicit control over rules that may differ by employee or department.

For example, a promotion may lead to an updated flight cabin rule, a department move may change the appropriate approver, or a new sales region may call for different lodging thresholds. The HRIS maintains eligible employee data, while administrators apply the corresponding travel policy settings and approval routing.

For access governance, the implementation plan should include an immediate suspension process alongside scheduled roster synchronization, with tests for account permissions and active sessions. This is a standard safeguard for any system that combines periodic employee updates with authenticated application access.

Simplifying Access with Single Sign-On Integration

Single sign-on, or SSO, lets employees use a configured corporate identity provider to access business applications. It supports a consistent authentication process across the organization and helps IT administrators manage sign-in requirements centrally.

SSO, Provisioning, and Access Revocation

Three identity functions should be distinguished:

• Authentication: SSO, often implemented through SAML, establishes the employee's identity when accessing an application.
• Provisioning: A supported lifecycle process creates, updates, or disables an application account. Just-in-time account creation and SCIM provisioning are examples of separate methods.
• Session management: Access policies and revocation procedures govern the continuing use of previously authenticated sessions.

The technical separation matters because changing an employee's corporate identity status, modifying an application account, and ending an existing session are different operations. Microsoft's SSO configuration guidance and provisioning documentation describe these distinct mechanisms.

Engine's HRIS, ERP, and SSO integrations are scoped around the identity provider, protocols, provisioning workflow, and account requirements of the deployment. This makes identity planning part of the overall travel program configuration.

A Practical SSO Implementation Sequence

An enterprise SSO rollout can follow these steps:

• Define identity ownership: Document the identity provider, authoritative user identifiers, application access groups, and administrators responsible for the connection.
• Configure the authentication exchange: Where SAML is selected, establish application metadata, entity identifiers, assertion consumer details, required claims, and signing certificates.
• Set account lifecycle rules: Align SSO access with the chosen employee provisioning method and the HRIS account roster.
• Test representative scenarios: Include first-time sign-in, existing users, changed identities, terminated employees, access restrictions, and session revocation.
• Monitor authentication events: Use identity-provider sign-in and audit logs alongside the relevant travel application administration controls.

A controlled pilot with representative employee roles helps the organization establish its access procedure before broader rollout. Microsoft's session revocation guidance explains why identity and active-session controls should be tested as separate parts of offboarding.

Connecting Travel Booking to Expense Management

Travel booking and expense management overlap, but the records they process differ. A booking platform supplies itinerary and trip context. An expense workflow may also need receipts, card transactions, employee-paid items, reimbursement categories, and accounting approvals.

What Expense Integrations Need to Exchange

A useful data model separates the following records:

• Itineraries and reservation details: Traveler, travel dates, destination, booking reference, and estimated cost.
• Final receipts and hotel folios: Supporting documentation for completed services and itemized charges.
• Consolidated company bills: Statement-period charges, vendor references, adjustments, and company accounting context.
• Corporate card transactions: Payment activity associated with a cardholder, category, transaction date, and merchant.
• Employee reimbursements: Out-of-pocket expenses and any separately administered mileage or per diem rules.

Not every organization needs the same records to flow through the same connector. A company that pays for eligible travel through DirectBill can use consolidated billing for its accounting process, while an employee-funded meal may still follow an established expense reimbursement procedure.

Engine's accounting integrations help carry configured financial billing records to supported accounting systems. Its Engine X charge card adds cardholder transactions, category controls, and spend visibility within the Engine environment. These mechanisms complement the company's existing treatment of receipts, reimbursements, and ledger approvals.

Reducing Manual Expense Work Without Losing Control

The useful automation opportunities are precise: carry a traveler or project reference forward, classify invoice types, populate a supported accounting dimension, and make billing records easier to trace. The control requirements are equally concrete: maintain valid account mappings, retain appropriate supporting documents, review exceptions, and reconcile posted totals.

Engine's Travel Reporting and Analytics brings booking and billing records into a central view with filters for company-defined context such as project, team, department, job code, and cost center. The custom reporting guide also documents reusable report configurations, selectable fields, and scheduled reports. Finance can use these views to support reconciliation and budget analysis while preserving the accounting system as the ledger of record.

The Operational Benefits of Connected Travel Management

Connected travel systems can improve coordination among travel, finance, HR, and IT. Outcomes should be tied to measurable processes rather than broad claims about automation.

Metrics That Show Whether Integrations Work

A useful performance review can include:

• Manual entry volume: The number of eligible bills or employee updates that require repeated input.
• Mapping accuracy: The proportion of transferred records reaching the intended GL account, department, or project.
• Exception resolution: The number, cause, and age of synchronization errors awaiting attention.
• Close-cycle effort: Finance hours spent reconciling travel statements and related card transactions.
• Policy administration: The number of employee changes that require a corresponding policy or approval adjustment.
• Access governance: Completion of new-hire provisioning, termination archiving, and session management tests.

Engine's accounting sync views, travel policy controls, and central reporting provide mechanisms that support these kinds of operational reviews.

Planning for Organizational Change

Integrations also matter when a business adds departments, opens offices, restructures accounting entities, or acquires another company. The design should preserve a clear source of truth for employees, vendor records, organizational dimensions, and booking history.

International operations introduce additional decisions about currency, tax treatment, access permissions, and cross-border information flows. Under the GDPR, international transfers are governed by data transfer rules, which are distinct from a universal requirement to host all data in a particular region. The organization should document its relevant legal and security requirements as part of integration design.

How to Evaluate Travel Management Integration Capabilities

The evaluation should be based on a representative end-to-end workflow: an employee is created, books a trip, receives any required approval, incurs eligible charges, and has the resulting billing records recorded in the correct finance process.

Integration Evaluation Criteria

• Object coverage: Identify the exact supported booking, employee, bill, card, and reporting records.
• Operation coverage: Distinguish read, create, update, archive, posting, and status-return actions.
• Field coverage: Identify required and optional values, valid-value restrictions, and the system that owns each field.
• Timing: Record the scheduled or event-driven trigger for each data exchange.
• Security: Document access roles, credentials, token handling, and offboarding procedures.
• Financial controls: Include legal-entity selection, GL coding, currency treatment, tax, and reconciliation.
• Monitoring: Include status visibility, retries, exception ownership, and audit trails.
• Export and retention: Establish which reports, supporting documents, and historical records must remain accessible.

For Engine, the QuickBooks configuration guide, NetSuite configuration guide, and HRIS synchronization guide provide documented starting points for an object-level evaluation. They show why connector-specific mappings and triggers matter more than a single integration label.

Architecture and Data Governance

APIs, file exchanges, direct connectors, and integration middleware can all move business data. The appropriate design depends on the records involved, authentication model, permissions, audit needs, and supported transfer methods.

A secure integration assigns clear data ownership and limits access to the records required for each workflow. It also distinguishes operational reporting from a full historical archive, since a downloadable report and an application data backup serve different purposes. These principles are relevant to finance integrations, HRIS synchronization, and SSO alike.

Implementing Travel Management Integrations: A Phased Plan

A phased rollout helps a company establish permissions, mapping accuracy, and reconciliation procedures before expanding the program. The phases below are arranged by dependency, with identity and access controls addressed at the outset.

Phase 1: Identity, HRIS, and Access Controls

• Assign owners for HR data, identity administration, travel policies, and account offboarding.
• Configure the eligible Engine HRIS connection and define the employee groups and profile fields in scope.
• Establish the selected SSO configuration and account lifecycle process for the deployment.
• Test new hires, employee changes, terminated accounts, urgent suspension, and active-session behavior.
• Establish administrative ownership of travel policy assignments and approval routing.

Phase 2: Accounting and Billing Configuration

• Document the chart of accounts, vendor references, invoice types, and supported organizational dimensions.
• Configure the applicable QuickBooks Online integration or NetSuite integration using its documented authentication and mapping process.
• Run the connector's prescribed test invoice and review the resulting financial record.
• Use representative billing transactions to assess line-item classification and custom-field values.
• Establish statement-cycle reconciliation and responsibility for transfer exceptions.

Phase 3: Expense, Policy, and Reporting Workflows

• Define how company-paid and employee-paid expenses enter existing approval and reimbursement processes.
• Configure Engine travel policies, Engine Approvals, and the booking fields needed for cost allocation.
• Align applicable Engine X spend controls with cardholder and accounting responsibilities.
• Build reusable reports for finance and travel administrators using supported fields and filters.
• Test representative travel scenarios, credits, adjustments, and report outputs.

Phase 4: Monitoring and Continuous Maintenance

• Assign owners for integration credentials, mapping changes, and employee data administration.
• Monitor accounting bill synchronization and employee roster changes.
• Review mapping exceptions and repeatable corrections as business structures evolve.
• Retest affected workflows following material system or policy changes.
• Track reconciliation effort and exception volumes to assess operational improvement.

This approach makes the integration an ongoing business process rather than a one-time connector installation. Engine's onboarding resources support company setup and employee readiness alongside the organization's finance and IT responsibilities.

Why Engine Stands Out for Travel Management Integrations

Engine connects the travel booking experience with the controls that finance, operations, and IT teams use to manage business travel. Companies can book hotels, flights, and rental cars, manage requests for nine or more rooms through Engine Groups, and use Engine Spaces to discover meeting and event venues. That breadth supports common business travel scenarios, from conferences and sales trips to offsites and project-based travel.

The most relevant integration advantages come from Engine's documented financial connections and the administrative features that preserve business context from booking through reporting.

Engine QuickBooks Online, NetSuite, and Sage Intacct Integrations

Engine lists accounting integrations for QuickBooks Online, NetSuite, and Sage Intacct. Its detailed QuickBooks and NetSuite workflows use reference-data synchronization, GL account selection, custom-field mappings, test invoices, and statement-triggered bill transfers. Finance teams also receive billing sync-status views for following transferred records and managing mapping corrections.

For QuickBooks Online, the integration uses Merge authorization and offers simple or custom invoice mapping, including a PDF invoice attachment option. For NetSuite, the documented setup uses SuiteCloud services and token-based authentication, with a selected billing entity and accounting dimensions. These are specific, finance-oriented mechanisms rather than an unspecific promise of data connectivity.

Engine HRIS Integrations for Account Lifecycle Sync

Engine's HRIS synchronization supports employee account creation, profile updates, archiving, and restoration of matching archived accounts through supported Merge-connected HR platforms. Synchronization occurs approximately every 24 hours after the initial sync. Selective synchronization gives administrators control over eligible organizational groups, and policy assignments remain under the travel administrator's direct management.

Engine's ERP and SSO integration overview also provides a framework for aligning applicable financial and identity requirements with the company's existing systems.

Engine Omni Hotel Booking API

For software partners embedding hotel reservations in their own products, Engine Omni provides hotel discovery, rate shopping, offer confirmation, booking, and post-booking management interfaces. The documented API supports gRPC and HTTP/JSON, mutual TLS authentication, booking-event webhooks, and sandbox testing. Omni is a partner-facing hotel booking integration, distinct from Engine's accounting, HRIS, and SSO administration connections.

Engine DirectBill Consolidated Invoicing and Autopay

With Engine DirectBill, Engine extends a line of credit, pays hotels for eligible stays, and sends the business one consolidated invoice after stays. The company can manage eligible travel charges through its approved billing arrangement and associate relevant cost information with the resulting billing records. Payment terms and the credit arrangement follow the company's agreement.

Engine's billing tools provide access to itemized statements, available folios, and CSV or PDF exports for financial review. Autopay supports scheduled bank-account payments under the company's billing arrangement.

Engine Incidentals Coverage is a separately enabled add-on for eligible DirectBill stays at participating hotels. With Engine's Incidentals Coverage add-on, travelers skip credit card authorization forms at check-in. Covered charges and reservation eligibility follow the applicable property and program terms.

Engine Travel Policy Enforcement and Engine Approvals

Engine Travel Policy Enforcement applies configured lodging, flight, and rental car rules during booking. Administrators can set rate or cabin restrictions, assign policies to employees or departments, and select Not Allowed, Allowed with Reason, or Allowed with Approval for out-of-policy reservations.

Engine Approvals routes approval-required requests to configured administrators or department managers. Approvers can review the trip details and act on a request before the reservation is completed. This puts policy decisions into the booking workflow and makes exception handling visible to the responsible team.

Engine Travel Reporting, Custom Fields, and Scheduled Reports

Engine Travel Reporting and Analytics organizes travel booking and billing data using business context such as department, project, team, job code, and cost center. Finance teams can apply those dimensions to budget reviews and travel allocation analysis.

Engine's custom reporting tools also support selecting and reordering fields, saving reusable report configurations, scheduling reports, and sharing reports with Engine members. These features help teams establish repeatable reporting routines tied to the information captured during booking.

Engine X Business Charge Card and Spend Controls

Engine X is a business charge card that brings company card activity and Engine travel bookings into the same management environment. It supports virtual and physical cards, configurable spending controls, and cardholder transaction visibility. The card has no annual fee. All applications subject to credit approval. The applicable Engine X card terms govern the card program.

For finance teams, Engine X provides a connected source of card activity alongside travel booking and billing information, complementing the supported accounting integrations and established financial approvals.

Engine Groups Room-Block Sourcing

Engine Groups provides managed room-block sourcing and coordination for nine or more rooms, including conferences and company offsites. The core booking platform and Groups service are free to use. The Engine pricing page describes the core offering as: No platform fees, no membership fees, no agent-assist fees, no contracts, no minimum spend. Individual reservations and group room-block agreements retain their applicable booking terms.

Engine Flex and FlexPro Cancellation Coverage

Flex is a paid per-booking add-on for eligible hotel reservations. For qualifying flights, the separately purchased Flex for Flights add-on lets travelers cancel up to two hours before the first scheduled departure.

FlexPro is a paid company subscription that automatically applies Flex coverage to hotel bookings made while the subscription is active, including eligible nonrefundable rates. Covered bookings can be canceled until noon on the check-in day, and the default refund is a one-year Engine travel credit. See the FlexPro product information. Flex and FlexPro are paid products distinct from the free core booking platform and Groups service.

Engine 24/7 Live Support and Eva

Engine offers 24/7 live support by phone, chat, and email. Eva, Engine's AI assistant supports common travel requests, with escalation to live agents by phone, chat, and email. These support options serve travelers and administrators throughout the booking and trip-management process.

Frequently Asked Questions

What data residency options exist for international organizations using travel management integrations?

Data residency and international data transfer are related but different considerations. Organizations should document the location and access rules for employee and travel records, the applicable retention and security requirements, and the legal mechanism for cross-border processing. The GDPR's international transfer rules do not establish a universal requirement to host all personal data in the EU. A deployment's specific processing and hosting arrangements belong in the organization's technical and contractual assessment.

How do travel management integrations handle multi-currency expense processing?

Multi-currency processing depends on the accounting workflow and the supported transaction fields. Relevant data can include the original charge currency, ledger or functional currency, exchange-rate date, tax treatment, and reimbursement currency. The accounting design should specify which system applies conversion and how credits or adjustments are reconciled. For Engine accounting integrations, the precise currency data transferred and applied depends on the selected accounting connection and its configured mappings.

Does single sign-on automatically provision and archive traveler accounts?

No. SSO is an authentication method. Provisioning and account lifecycle management use separate supported processes, such as HRIS synchronization or an identity provisioning method configured for the application. Engine's HRIS integration provides documented employee creation, updates, archiving, and restoration of matching archived accounts through supported HR systems. Identity administrators also need a defined procedure for ending existing sessions when access is withdrawn.

What happens to integrations during software platform updates?

Software updates may affect permissions, accepted field values, data formats, or connector behavior. A sound maintenance process includes review of relevant changes, regression testing of affected identity and financial workflows, and monitoring after deployment. Engine's QuickBooks Online and NetSuite billing views support monitoring and managing bill synchronization results.

Can travel management platforms integrate with on-premises accounting systems?

Integration with an on-premises system depends on the accounting application's supported interfaces, network access, security model, and the connection design. Technical approaches may include a supported direct connector, managed file exchange, an integration gateway, or other approved middleware. The business should distinguish these architecture choices from the published scope of its travel platform's native accounting connections. Engine lists its available accounting integrations in a dedicated directory.

How should organizations manage a transition between travel platforms?

A structured transition establishes ownership of active bookings, outstanding bills, travel credits, identity access, and historical reporting. Finance and travel administrators can compare representative booking and billing outputs during a controlled parallel period, then use agreed acceptance criteria to complete the migration. Engine's reporting capabilities support review of recorded travel activity, while retention and archival requirements should be established in the organization's migration plan.