Moving from Cin7

Paste a Cin7 key and Manifold reads your account across: products, stock at every location, customers, suppliers and price tiers. Manifold only ever reads from Cin7. You keep using Cin7 until you go live.

What comes across

• Locations, products and variants, and kits.
• Price tiers, as catalogs. Each customer's tier, and a Cin7 Core customer discount, as the catalog their company buys from.
• Each SKU's average cost, as its cost in Manifold, and each supplier's prices.
• Stock on hand per location, with serials, batches and unit cost.
• Suppliers, customers and open purchase orders.
• Your order history, if you ask for it.

Not read: customer-specific prices, product discount rules and deals. Recreate contract prices as a catalog for the company, quantity discounts as quantity breaks, and deals in your store. See Catalogs and prices.

Still deciding? Manifold and Cin7 Core and Manifold and Cin7 Omni compare price, users and limits, each Cin7 figure linked to the page it came from.

Cin7 names, and where they are in Manifold

The Screens menu is at the top of the admin. It lists every screen, including those not in the sidebar.

1. Make a key in Cin7

Give Manifold its own API application, so you can delete it afterwards and end Manifold's access.

Cin7 Core (inventory.dearsystems.com)

Open Integrations › API, press +, name it Manifold migration and press Create. The Account ID and Key are on its Setup tab.

Cin7 Omni (go.cin7.com)

Open Settings › Integrations & API › API v1 and choose Add New API Connection, named Manifold migration. Copy the API username and API key now: Omni shows the key only once. Under the connection's Permissions, allow Read only, on Branches, Products, Stock, Contacts, Purchase Orders, Sales Orders and BOM.

2. Paste it into Manifold

1. In the setup walk's Add your products and stock step (or Settings › Setup), choose the migration.
2. Under Which system, choose Cin7 Core or Cin7 Omni.
3. Choose what to bring: on-hand stock, suppliers and customers, open purchase orders, and order history. Order history is off by default: Cin7 Core is read one order at a time, so a long history takes hours.
4. Leave Keep following this account until I go live ticked, unless you want a one-off import.
5. Paste the two values and press Preview the migration.

Reading a large account takes a while: Cin7 Core answers about one request a second.

3. Check the preview

The preview changes nothing. It counts what will come across and the stock value, and lists warnings:

SKU not importable

Manifold SKUs are letters, digits, - and _. Fix the SKU in Cin7, or recreate the product here afterwards.

Assembly products carried as plain stocked SKUs

Finished goods come across as stock. The assembly recipe does not.

Average costing

Manifold values stock first in, first out, so its valuation differs slightly from Cin7's average cost.

Stock lines with no unit cost

They come in without a cost. Fix the cost in Cin7 first, or give it on your opening stocktake.

Tracked stock without serial or batch numbers

Units Cin7 cannot name are not brought in. Count them once the migration is in.

When the preview looks right, press Apply to Manifold. Manifold then shows, per SKU and location, what Cin7 said against what Manifold now holds.

If the preview failed with a refusal from Cin7, the values were pasted wrong or an Omni permission is missing. Start again with the right values. Otherwise, run one migration per organization: a second one brings the opening stock in again.

4. While Manifold follows Cin7

The badge at the top reads Read-only · following Cin7. Manifold re-reads Cin7 on a schedule: new products, customers, suppliers and orders come in, and stock is corrected to Cin7's figures. Keep working in Cin7. Products, stock, orders, purchasing, customers and the other areas Cin7 feeds can be read here but not edited.

Settings › General shows the link and its recent syncs, with Sync now and Stop following. A record Manifold refuses three times is set aside, and the sync names it: fix it in Cin7 and it is picked up again. If Cin7 refuses three syncs in a row, usually because the key was deleted, your owners and admins get an email.

Keep the Cin7 API application until you go live: deleting it early makes every sync fail.

5. Shopify

Connect your Shopify store now, while Cin7 still runs it. Manifold sends nothing to the store until you go live: orders come in and you can check them against Cin7, but stock and prices stay as Cin7 sets them. Connect it in the setup walk, or in Settings › Sales channels, and take its Bring in what the store already has step. See Connect a Shopify store.

On the day you go live, turn off Cin7's Shopify integration just before you press Go live. From then on Manifold sends the store its stock. See the switch-over checklist.

6. Going live

1. Count and cost your stock on the opening stocktake. You can do this while Manifold follows Cin7.
2. Go live (see Read-only mode and going live). If you brought order history, one last read of Cin7 turns the orders still open there into live orders here. Then the link ends, the key is destroyed and the records Cin7 fed become editable.
3. Stop using Cin7 for the same work, and delete the Manifold migration application there.

Let an agent do it

An AI agent can do everything here except the paste, which stays yours because the key is a credential. See the Cin7 migration skill and AI agents.