Skip to main content
Aria Knowledge Central

Copy Configuration Overview


Aria's Copy Configuration functionality allows you to export the configuration data of an Aria Billing Cloud instance. You can then import the configuration file created by the export process to populate another Aria instance with the same or similar configuration data. One application of Copy Configuration is exporting configuration data from a testing environment and then importing the data into a live production environment.

Note: Not all objects and elements of the system are exported. Refer to the Copy Configuration Best Practices section for a list of system characteristics that are not exported.

Copy Configuration exports the following system objects and elements:


  • Reason Codes
  • Payment Terms
  • GL Codes

Product Catalog

  • Plans
  • Plan Groups
  • Plan Exclusions
  • Non-subscription Offerings
  • Usage Types
  • Services (including mapping to tax groups and GL Codes)
  • Coupons
  • Credit Templates
  • Discount Rules
  • Discount Bundles
  • Promotions
  • Promotional Plan Sets

Client Configurations

  • Billing
    • Countries
    • Currencies
    • Chart of Accounts
    • Batch Processes
    • Invoice Settings
    • Taxation Settings
  • Payments
    • Payment Methods
    • Dunning Processes
    • Payment Settings
  • Notifications
    • Events
    • Email Templates
    • Notification Settings
    • Notification Template Groups
    • Provisioning Settings
    • Email Template Fields
  • Integrations
    • Tax Service Groups
  • Security
    • Roles
    • Account Access
  • GL Code Mappings
    • Services
    • Transaction Types
    • Credit Cards
    • Payment Methods
  • Client Settings
    • Company Profile
    • Account Fields
    • Product Fields
    • Functional Account Groups
    • Miscellaneous Settings
    • Account Creation
    • USS Reg Configuration
  • Other client configurations not displayed on the UI:
    • Statement templates
    • Custom report definitions
    • Custom reason codes for credits, refunds and write-offs
    • Plan_pay_notify_email mapping for plans so that CSRs
      have the correct options in account overview when
      updating pay method or notify method
    • Credit limits
    • Refund limits
    • Service groups
    • Special batch process schedules and dependencies
    • Custom user roles
    • Client default table
  • Was this article helpful?