Migrate from Logo Go to Acumatica

Logo Go customer records map 1:1 to Acumatica Customers. Contact name, email, phone, and address fields move directly. Logo Go customer IDs are stored as a custom field (Logo_Go_Customer_ID__c) for traceability and delta-run de-duplication. Tax ID fields map to Acumatica's Tax Registration ID on the Customer screen.

Logo Go subscriptions do not have a native Acumatica equivalent. FlitStack converts each active subscription to an AR Invoice schedule (if recurring) or to a set of open AR Invoices with original subscription amounts. Closed/cancelled subscriptions migrate as historical invoice records. The subscription status (active, trialing, cancelled) becomes a custom Subscription_Status__c picklist on the Customer.

Logo Go usage records (metered-consumption events) have no Acumatica counterpart. FlitStack stores per-subscription usage totals as custom Number fields (e.g., Usage_Qty_Month__c, Usage_Unit__c) on the Customer record. If usage feeds billing, the usage total is applied to an AR Invoice line item with a note explaining the conversion source.

Logo Go plans map to Acumatica Products (for metered/service items) or Stock Items (for one-time products). Plan pricing becomes the Product's default price. The plan's billing frequency (monthly, annual) maps to the billing frequency on the Customer or to a Subscription Schedule in Acumatica.

Logo Go amendments (mid-cycle plan changes) and add-ons are captured as custom Amendment_Type__c and Amendment_Amount__c fields on the Customer record or as separate AR Invoice line items with descriptive notes. Historical amendment logs are preserved as a related note on the customer account.

Logo Go coupon codes and discount rules are stored as custom fields (Coupon_Code__c, Discount_Pct__c) on the Customer or AR Invoice. Acumatica has no native coupon engine; discounts are applied manually or via AR invoice adjustments at migration time. Any recurring discount logic requires rebuilding as an Acumatica customization or a manual review step in the AR workflow.

Logo Go invoices map directly to Acumatica AR Invoices with original invoice date, invoice number, line items, tax amounts, totals, and payment status preserved. Closed invoices load as completed AR Invoices (no further editing). Open invoices load with their current status. The Logo Go invoice ID is stored as a custom reference field for reconciliation.

Logo Go payments are applied to Acumatica Payments linked to the corresponding AR Invoice. Original payment date, amount, and payment method type are preserved. Payment method tokens (credit card references) cannot migrate — payment gateway re-enrollment is required in Acumatica's Payments module post-migration.

Logo Go customer tax IDs map to the Tax Registration ID field on the Acumatica Customer. Acumatica's Tax Zones and Tax Categories must be configured before migration so tax is calculated correctly on invoices going forward.

Logo Go contact records become Acumatica Customer Contacts. Primary contact maps as the default contact. Additional contacts are added as related Contact records with their role (Billing, Technical, etc.) from Logo Go's contact type field. The contact role designation ensures invoices and statements route to the correct person within each customer account.

Logo Go billing and shipping addresses map to Acumatica Address book entries on the Customer. Address fields (street, city, state, postal code, country) transfer directly. The address type (billing vs. shipping) is captured in the Address Name field or in a custom Address_Type__c field to preserve the original address purpose in Logo Go.

Logo Go credit notes require review against Acumatica's credit memo configuration. Some setups use AR Invoice Reversals; others use AR Invoice Adjustments. FlitStack documents the approach before migration based on your Acumatica Accounts Receivable configuration. The chosen method is applied consistently across all credit note records during the migration run.

Logo Go custom objects migrate to Acumatica as custom fields on the Customer, Subscription, or Invoice screens, or as custom database tables if the object has independent records. The migration plan documents the target screen and field type before data loads. Custom object relationships are preserved via reference fields or lookup fields in the Acumatica schema.

Logo Go file attachments (contracts, plan PDFs, invoices) associated with customers or subscriptions are downloaded and re-uploaded to Acumatica's Note system or Document Management (DMSE) module linked to the corresponding Customer or Invoice record. File size limits apply per Acumatica's document storage configuration.