Migrate from Opera 3 to HubSpot

Opera 3 Sales Ledger accounts map directly to HubSpot Companies. The SL_Account_Ref field becomes Source_System_ID__c on the HubSpot Company for full traceability back to the source record. Standard Company properties such as name, address fields, telephone, website, and industry are populated from the corresponding Sales Ledger columns. Financial summary fields like account balance and credit status transfer as custom properties. Accounts showing zero balance or prospect status in Opera 3 map as-is without any transformation.

Individual contact records stored within Opera 3 Sales Ledger accounts migrate as HubSpot Contacts. Each contact's parent SL_Account_Ref links to the corresponding HubSpot Company via the standard company association mechanism. Multiple contacts per account are preserved as separate HubSpot Contact records, each retaining a custom property that stores the original department or role designation from Opera 3 for complete organizational context.

Opera 3 Purchase Ledger suppliers map to HubSpot Companies with a custom Supplier__c boolean property set to true. Suppliers are treated as Companies rather than Contacts since HubSpot's contact model is person-centric. Financial terms and credit limits from the PL record migrate as custom properties for reference.

Each Opera 3 SOP order header — containing order number, customer reference, order value, and status code — maps to a HubSpot Deal. The order status code (e.g., 'Entered', 'Despatched', 'Invoiced') maps to a HubSpot Deal stage via a value-mapping table. The original SOP order number is preserved in Source_System_ID__c.

SOP order lines map to HubSpot Deal line items within each Deal. Product description, quantity, unit price, and discount percentage are mapped to the corresponding HubSpot line-item properties. Multiple line items across an SOP order collapse into a single HubSpot Deal with all line items attached.

Opera 3 Stock Control items map to HubSpot Products. Product code, description, unit of measure, standard cost, and selling price translate to corresponding HubSpot Product properties. The product code maps to hs_sku, description to name, standard cost to cost, and selling price to price. HubSpot's product library enables the product picker functionality on Deals once the migration run is complete, allowing your sales team to associate migrated products with new deals directly within HubSpot's interface.

Opera 3 Nominal Ledger accounts represent the chart of accounts — a purely accounting concept with no HubSpot CRM equivalent. These are migrated as a custom object for reference and reconciliation purposes. The nominal code, account name, and category (e.g., 'Cost of Sales', 'Overhead') are stored as custom properties. Financial reporting based on nominal codes must remain in Opera 3 or your accounting tool.

Opera 3 SOP orders with currency codes (GBP, EUR, USD) are handled by storing the raw amount as a custom Deal property (Original_Amount__c) and the currency code as a separate text property (Original_Currency__c). The converted base-currency amount from your Opera 3 exchange rate table maps to the standard HubSpot Deal Amount field.

Closed invoices and credit notes from Opera 3 are migrated as historical Deals in a 'Closed Won' or 'Closed Lost' stage with invoice number preserved in a custom property. This gives your HubSpot reporting continuity with past transaction history without creating active pipeline noise.

Opera 3 user logins resolve to HubSpot Owners by email address match. FlitStack AI flags any Opera 3 user without a corresponding HubSpot user before migration. Unmatched users can be invited to HubSpot first, or their records are assigned to a designated fallback Owner during the migration run.

PDF documents stored against Opera 3 records — invoices, statements, remittance advices — are downloaded and re-uploaded to HubSpot Files, linked to the relevant Company or Deal record. File size limits (Sales Ledger attachments) are respected during the re-upload process.

Opera 3 user-defined fields stored as arbitrary database columns require type inference before mapping — text fields become HubSpot string properties, numeric fields become number properties, date fields become date properties. FlitStack AI surfaces all custom columns during the audit phase and creates the corresponding HubSpot properties before the migration run.